Order JC 7232.15 Safety Risk Management Implementation for Central Service Area
This document is no longer current. Cancelled by JO 1000.37A. Check the official source before relying on it.
Federal Aviation Administration
Memorandum
Date. SEP 3 0 2008
To M~~ploye.B:~~entral Terminal Operations
From: :JaXtik~~or of Terminal Operations, Central Service Area
Subject: Central SerYice Area, Safety Risk :Management Implementation
FAA Order JC 7232.15, Safety Risk Management Implementation. effective October l. 2008. establishes DistrictFacility responsibilities and procedures to achieve Safety Risk Management: (SR.t\1) compliance \s.ithin the Central Terminal Senice Area (CTSA). The Order serves as a supplement to the ATO Safety Management System (SMS) Implementation Plan by providing implementation guidance for the CTSA.
Order JC 7232.15 clarifies procedures used for routing ofSafety Risk Management Documents (SRMDs) and Safety Risk Management Decision Memorandums (SRMDMs) v..ithin the CTSA. In addition, Order 7232.15 v..ill provide further darification ofthe District and Facility Offices. as well as the Senice Center roles and responsibilities for continued S~\1 compliance in the CTSA.
All Facility and District Offices requesting changes to Terminal Airspace and procedures, including waivers and/or waiver renewals, shall submit those requested changes along with
appropriate SRM documentation to Operations Support Group (OSG), AJV -C2.
Each Support Specialist ""ithin the OSG \vill sen·e as the primary District/Facility interface for airspace and procedural changes requiring Safety Risk !\fanagement (SR..\.1). The Operations Support Specialist \\ill coordinate subsequent documentation '.\ith the Safety Assurance Group. AJV-Cl.
If you have any questions regarding SMS or integration of S~\1 in the CTSA, please contact Sharon Rushing, Central Sen'ice Center, Safety Assurance Group (AN-Cl2), at (8 1 7) 222 4714, or Dennis Hinton, Central Service Center, Safety Assurance Group (AJV-C12), at (817) 222-4566.
U.S. DEPARTMENT OF TRANSPORTATION ORDER FEDERAL AVIATION ADMINISTRATION JC 7232.15 CENTRAL SERVICE AREA
Eiiective Date:
09130/2008
SUBJ: Safety Risk Management Implementation for Central Service Area
1. Purpose of this Order. This Order supplements the Air Trafiic Organization lATO) Safety \1anagcmcnt System tS\1S) Implementation Plan bj pro\iding implementation guidance for the Central Tenninal Sel'ice Area (CTSA).
2. Audience. All Central Terminal Senice Area (CTSA) personnel should read and be farniliar"ith this order.
3. \\'here Can 1 Find tbi Order? This order is a\ ailable to anyone in the F :\.-\ at htrps:. 'ksn.1aa.g0\ km teams atotsms and https: emplo\ees.faago\. tools resources. orders notices.
-'· CanceUation. ~ot Applicable
5. Background. A\iation safety is a fundarnemal mission ofthe Federal A\iation . \dministration (FAA). In accordance v.ith Annex 11 to the Con\'ention on International Ci\il A\iation. Air Traffic Serl'ices. FAA Order ll00.161. Air Traffic Safto Orersight. and A TO Order JO 1000.37. Saftry .\lanagement S.l-~'ltem. the ATO has implemented a fom1al Sl\ fS program. The SMS program requires a Salet) Risk Management (SRM) analysis be conducted and supporting documentation referred to as a Safety Risk Management Document (SRMD) or Safet) Risk Management Decision Memorandum (SRMDM). be prepared and retained for all changes impacting the National Airspace System (NAS). SRM analysis must be conducted prior to any change or modification to tenninal airspace procedru-es. change or modification to tem1inal NAS systems. and prior to submitting any request for waiver ofair
traffic control requirements identified through FAA Order .10 7110.65.
6. Explanation of Policy C hanges. This order establishes District/Facility responsibilities and procedures to be utilized to achieve Safety Risk Management (SRM) compliance within the CTSA.
7. SMS Policy. A 1 0 Order JO 1000.37. Sqfety "\fanagement Systern. defines the policy. application. and supporting documents ofthe SMS within the ATO. It identifies the strategic and tactical safety responsibilities ofall ofthe Sel'·ice Units: addresses the requirements. safe!} standards. and guidance under \\ hich the A TO operates: and establishes the SMS policy all A TO personnel must adhere to.
8. SMS Objectives. The o' ernrching objectiYe of the Safety Management System (S~1S) is to increase the safety ofthe :\AS by reducing the potential for accidents and by knov.ingly accepting appropriate risk into the '\AS. The SMS introduces SR\.1 capabilities needed for aS) stematic approach to managing the sate~ risk ofAir Traffic Control (ATC) and na\·igation sel'\ices.
9. Accountable O fficials. The Director of Central Terminal Operations (AJT-C) is accountable for implementation of the SR.\1 process "'ithin the CTSA and has the responsibility to fulfil] the requirements of this order.
Distribution: Electronic Initiated By: AN-C12
JC 7232.15 09/30/2008
10. Distribution. This order is distributed to the Director, Tenninal Operations, all Terminal Facilities in the Central Service Area, Central Planning and Requirements Group, Central Operations Support Group. and the Central Safety Assurance Group.
11. Scope. This order outlines responsibilities and procedures for the training ofpersormeL the preparation and coordination ofSRM documentation. and the exchange ofinfonnation within CTSA as it pertains to the SR.t\.1 process. Additionally. it addresses procedures to be used in requesting support for SRM projects.
12. Responsibilities.
a. Facility/District Air Traffic Managers (AIMs) must:
(1) Ensure the SRM process is implemented. resourced, monitored. and evaluated.
(2) Designate District SRM Focal(s) to support the SRM process.
(3) As appropriate. designate a Facility SRM Focal to support the SRM process.
(4) Ensure all CTSA personnel receive the appropriate training (see Appendix A Training Comses for available SMS/SRM training). This must be in conformance with national policy and directive established v..ithin the Tem1inal Operational Services Unit.
(5) Ensure all SRMDs and SRMDMs initiated at the Facility/District level are coordinated
~ith the appropriate offices based on level(s) ofthe risk identified (see Appendix C for coordination/routing ofdocumentation based on the level of risk).
(6) For SRM activities impacting the Airport Line ofBusiness, request airport Subject Matter Expertise (SME) support through appropriate Airport District Office' (ADO).
(7) Ensure that experts from all impacted lines ofbusiness and organizations are represented in the SRM process.
(8) Ensure copies ofall final (signed) SRMDs and SRMDMs are maintained on file and a copy is uploaded and available on the ATO-T Knowledge Sharing Network (KSN) at: https:/!ksn.faa.govlkm/teams/atotsms. Additionally. an electronic signed copy and the original word processed form (plus any Preliminary Hazard Analysis [PHA] and/or Comparative Analysis [CPA]) should also be provided to the Central Safety Assurance Group.
(9) Evaluate the process, procedures, and effectiveness ofthe SRJ\1 process.
(1 0) Make recommendations to improve the overall SRM process.
1 Refer ro ARP Safety and Standards Guidance Letter 08 -1. Interim Guidancefor Safery Management Svstems
(SAf,~)!Safety Risk ManagemenT Document (SRMD) Activities Requiring ARP Participation, for detailed guidance when requesting ARP SMEs.
JC 7232.15 09 '30/2008
b. Facility District afet: Risk yfanagement ( R..\ l) Focal(s) must. as necessary:
( l) Assist in determining whether local facility changes are satet) signitlcant and thereb~ requiring development ofan R..\1D or SR.\1D\1.
(2) Assist in identification ofSMEs as participants on SRM panels.
(3) Assist in ,·erifying that SR..\1 panel proceedings are effectivcl) documented and that all documentation is complete.
(4) Ensure all hazards are input tracked and maintained in the FAA·s Hazard Tracking System (HTS). which can be found on line at http://host.ato-p.faa.gov/htstest/login.cfin.
(5) Monitor e1Tectiveness ofhazard mitigation strategies.
(6) Ensur(: SRl\-1 documents (S~\IIDs. R..\·lD\'ls) are correct!~ formatted based on Je,·el(s) of identified risk: cYaluatc and/or suppon the lacilities in the assessment of these mitigation requirements. This ,,iJI include ensuring the proper documentation. updates. SR'vfD\f SR\10 coordination. correct signature leYels. and maintenan~e ofda1a within the FA.-\·s I IT is accomplished (see Appendix B Safety Risk \lanagement Decision Memoranda ( R..\10~1) Coordination and Signa~ and Appendix C- Sate~ Risk ~1anagernent Document (SR..\.-ID) Coordination and Signatures).
(7) Maintain a cop) ofall final and or re,ised (signed) S&\.1Ds and R..\fDMs developed v..ith.i:n the Central Terminal districts.
(8) Participate in all SRM meetings and teleconferences as requested.
(9) Coordinate SRM activities vvith the Central Service Center Safe[) Assurance Group SMS Coordinator.
It is anticipated the Central Service Center. Operations Support Group (OSG). the. afety Assurance Group (SAG). and the Planning and Reqwrements Group (PRG) will suppon the Terminal Operations Directorate by providing the necessary assistance as requested/required. These rna~ include:
c. The Central Sei\ice Center. OSG \\ill support the Terminal Operations Directorate by:
(1) Sening as the Sen-ice Center's entr) exit point for all SR.\1 correspondence associated '"ith terminal airspace andlor terminal ATC procedural changes.
(1) Re' ie'\ all SR.\IDs and SRMD~fs fTom a technical perspectiYe to ensure compliance \\ith applicable directiYes (i.e .. 1--AA. JO 7110.65. FAA. .10 7210.3. etc.).
JC 7232.15 09/30/2008
(3) Forward all SRM documentation to SAG for review in accordance with Appendix B- Safety Risk Management Decision Memoranda (SRMDM) Coordination and Signatures and Appendix C - Safety Risk Management Document (SRMD) Coordination and Signatures.
(4) NotifY originating office when SRM documents/decision memos fail to meet SRM requirements established by the ATO SMS Manual. ATO Order JO 1000.37. and this order.
(5) Ensure SRM documents (SRMDs/SRMDMs) are technically correct based on level(s) of identified risk.
(6) Maintain overall responsibility for processing airspace and proceduTes change proposals to the NAS. Provide the Director for Terminal Operations proposals concurred with by both the OSG and SAG or when necessary those which should be rejected (this on a case by case basis)..
(7) Upon approval/disapproval by Terminal Operations Director. notifY originating office and f01ward copies of (approved) proposal to appropriate Headquarters offices.
d. Central Service Center. SAG will support the Central Terminal Operations Directorate by:
(1) As necessary provide SMS/SRM support and provide clarification ofSMS requirements.
(2) When necessary. facilitate and assist in establishment ofSRI\1 Panels.
(3) When requested. assist Facility/District Offices with writing ofSRMDs and SRMDMs.
(4) Review SMS/SRM documentation (SRMDs and SRMDMs) from a process perspective to ensure adherence with ATO SMS Manual. ATO JO 1000.37, FAA JO 1100.161. and this Order. Following the review. retum conunents to the OSG for a consolidated response to originating district/facility office.
(5) Assist in hazard identification by conducting safety data "mining .. and safety data analysis ofPilot Deviat.ions (PO), Operational Error (OE). Operational Deviation (OD). accident/incident reports. maintenance logs. etc.
(6) Ensure all initial high as well as residual medium and low risk hazards are entered in the HTS and each hazard mitigation strategy is monitored and tracked by the Facility/District. The SAG will support by ensuring risk levels associated v.-1th initial high and medium risk level hazards are monitored and tracked throughout the lifecycle of the change or unti I risk is mitigated to a low risk
level.
Ensure SRM docmnents (SRMDs/SRMDMs) are accurate. correctly formatted. complete, thorough. properly based on Jevel(s) of identified risk. display coiTect signature levels, and are coordinated/routed through approp1iate offices (see Appendix B- Safety Risk Management
JC 7232.15 09/30/2008
(7) Decision Memoranda (SRMDM) Coordination and Signatures and Appendix C Safety Risk Management Document (SRMD) Coordination and Signatures for SRMDMISRMD coordination and routing).
(8) Conduct monthly CTSA telephone conferences (telcons) with District/Facility SRM Focal(s) and actively participate in National telcons with the A TO Terminal Safety and Operations Support Of£ce, Senior Satety Engineer Group (AJT-28). CTSA telcons will address topics regarding SMS and SRM implementation within the Service Area at the faci lity/district level. while it is anticipated National tel cons will address SMS and SRM implementation topics common to all Service
Areas.
(9) As necessary. for those SRM activities impacting Airports Line ofBusiness (ARP), the Central Service Area SAG will suppott requests for airport SME suppo11 through Regional Arrports Division Manager.
( l 0) Serve as the primary interface with the Terminal Safety and Operations Support Office. Senior Safety Engineer Group (AJT-28). on terminal SMS policy and terminal SRM implementation.
e. The Central Service Center, Planning and Requirements Group (PRO) will support the
Terminal Operations Directorate by:
(1) Serving as the Service Center's entry/exit point for all SRM correspondence a<;sociated with temunal systems. equipment. and service changes.
(2) Provide SME support as necessary to SRM panels
(3) Review all SRM documents (SRMDs) and decision memos (SRMDMs) from a technical perspective to ensure compliance with applicable directives (i.e., installation and siting orders, handbooks, maintenance directives, etc.).
(4) Forward all SRM documentation to the Safety Assmance Group (SAG) for review in accordance with Appendix B- Safety Risk Management Decision Memoranda (SRMDM) Coordination and Signatures and Appendix C- Safety Risk Management Document (SRMD) Coordination and Signatures.
(5) Notify originating oHice when SRM documents/decision memos fail to meet SRM requirements established by the ATO SMS Manual. ATO Order .TO l 000.37. and this order.
(6) Maintain overall responsibility for processing Tenninal systems. equipment, and service change proposals to the NAS and provide the Director for Terminal Operations only those proposals concLUTed ""ith by both the Planning and Requirements Group (PRG) and Safety Assurance
Group (SAG).
(7) Upon approval/disapproval by Terminal Operations Director, notify originating office and forward copies of(approved) proposal to appropriate Headquarters offices as necessary.
JC 7232.15 09 3012008
(8) Ensure R.\1 documents (SR~fDs R~ID~1s) arc technicall~ correct based on le\el(s) ofidemi lied risk.
7/t2JA:l;;~,__,- Nancy B. Kort, Director ofTerminal Operations. Central Service Area
JC 7232.15 09 30'2008
Appendi.~ A
Appendix A - Training Courses
Appendix A - Training Courses
a. SMS/SRI"f Operations and Engineering Practitioners Course 6600000~ : This course is required training for all District/Facility SRM Focals and facilitators. Disuict and Facility Managers are also encomagcd to take this course.
b. ATO-T SR.\1 Implementation Workshop: Workshops arc used to gain additional experience in conducting Tem1inal SRM analysis and for completing associated documentation. This
is required training for all District'Facili~ SRM Focals and high!) desirable rraining for facilit)
~lanagers. Operations ~lanagers. Frontline Managers. Suppon ~1anagers. and Suppon. Staff Specialists involved in making changes to the ~A .
c. SMS/SR"f v.·eb-ba ed training: \\·eb-based rraining is a\ ailable through the electronic Learning Management System (eLMS). Government employees can access this training using the following URL: https: 1 elms.dot.uovlleamerlogjn.jsp. Contractor personnel can access the training through the internet site at the foiJowi ng URL: http:t 'cminet.jccbi.gov/sms/.
1) Course 10603: Introduction to Safery J4anagement SyMenzs- This course is required training tor all Facility ~1anagers, Operations Managers. Frontline Managers. Suppon Managers, and Support Staff Specialists. F 1\A personnel and!or contractor personnel v.ith limited access to eLMS may complete course l0603 'ia Computer-Based Instruction (CBI).
2} Course 66000001: nze J.rlmwger \Role in Sa(ery Risk Jfmwgemem - fhis course is required training for all Facili~ \1anagers.lt is also highl~ desirable training for Operations \tanagers. Frontline :\1anagers. Support l\1anagers. and Suppon StatfSpecialists.
A - l
JC 7232.1 5 09/30/2008 Appendix B
Appendix B - Safetv Risk Management Decision Memoranda (SRMDM) Coordination and Signatures
Appendix B - Safetv Risk Management Decision Memoranda (SRMDM) Coordination and Signatures
When proposing a change to the NAS, a preliminary satety analysis must be performed. Ifthe preliminary safety analysis indicates the change will not introduce 1isk into the fAS. documentation supporting the conclusion. a b1ief reasoning/motivation for the change, and rationale for not requiring further SRM analysis. should be presented in a Sqlety Risk Management Decision Memorandum (SRMDM).
a SRMDMs are required to have a minimum ofthree signatures - one from the Facility or Support Manage1.2 responsible for the change (change proponent) and one from a management official preferably from outside the facility. Ifthe Change Proponent is a Facility Manager or Support Manager, then the District Manager will provide the second signature. The third signature will be through Central Safety Assurance Group (SAG). By signing the SRMDM. the Change Proponent and/or Manager certify that the proposed change \\ill not adversely affect safety or introduce 1isk into the AS. The third signatory ft.mctions in a quality assurance capacity, endorsing both the preliminary safety analysis and the SRM decision process.
b. Electronic copies offinalized SRMDMs along with somce mate1ial must be forwarded to the Facility's/Districfs respective Support Specialist in the Operations Support Group (AJV-Cl). The OSG will review SRMDMs from a technical perspective and forward to the Safety Ass.wance Group (SAG) who will review the memorandlllll from an SRM process perspective. The SAG will, if
necessary, return comments to the OSG for a consolidated response to the miginating Facility/District o11ice.
c. SRMDMs are to be mruntained in the local Facility/District SRM File for a period equivalent to the lifecycle ofthe change. Finalized (signed) SRMDMs are to be uploaded and available on the ATO-T Knowledge Sharing Network (KSN) at: https://ksn.faa.govlkm/teams/atotsms.
d. A copy ofall signed SRMDS will be sent to the Central Safety Assmancc Group (SAG). The preference will be in electronic scanned fonnat, along with an electronic file copy ofthe final word processed SRMDM.
, - ATO Tenninal Managers are required to complete CotrrSe I0603. Introduction to Safe!) Management Systems, and CotrrSe 6600000 I. The Manager·s Role in Safety Risk Management prior to approving an SRMDM.
B - 1
JC 7232.15 09 3012008 Appendix C
Appendix C- afetr Risk Ylanagement Document (SR,fD) Coordination and ignatures
Appendix C- afetr Risk Ylanagement Document (SR,fD) Coordination and ignatures
Salet} Risk Management Documents (SRMDs) initiated by Facility!District office~ are coordinated and routed based on level(s) ofrisk and mitigation(s) required to control Lhe risk. Risk is assessed in accordance with the A TO SMS Y1anua13 with level ofrisk determined as High. Medium. or Low.
1. Initial High Risks4 - The 'RAID must be coordinated and routed through the follov.ing offices:
a Terminal t-acility District ~tanager. The lnitiating Facility ""ill coordinate route SR. \IDs through the Terminal District O!Tice. The District Office SR.J\11 Point ofContact (POC) ''ill revie'' and then wiJI coordinate'route to the Operations Support Group ( OSG ). Ifthe District Office is the
initiator, then the District Office will coordinate ""ith and rome SRMDs to the OSG. As soon as practicable. the iacility/district manager should notify the Safety Assurance Group (AJV-Cl) of the proposed change and the associated initial high risk hazard (HRH).
b. Operations upport Group (AN-C2). The OSG v.ill re\ie'' SR.'\1 documentS rroma technical perspective and fomard to the Sati:!t} .\ssurance Group (SAG). The SAG ''ill revie\\ the documents from a ate~ Risk \1anagement process perspecti\e and if necessary pro,ide comments and or recommendations to the 0 G. The SAG and OSG jointly \Vill coordinate through Terminal Airspace. Procedur~s. and Safety Groups (A.I f-28) for AOV approval ofinitial HRH mitigations. SRMDs which meet requirements established in the ATO SMS Manual and have received AOV concmrence throughout each SRM phase identified in Safety Oversight Circulars (SOC) 07-02 and/or SOC 07-05. will be forwarded to the Director ofCentral Icrrn.inal Operations. The SAG and OSG member revie"' ing rhe SR\1 document will indicate b~ signing they have rc,iev..ed and are in concurrence ,,;th the contents. SR.\1 processes. and format ofthe documem. Should the change require in\'OlYemem by the Planning and Requirements Group (PRG). the R.\ID ,,;ll be
coordinated'routcd to the PRG for their re\ie\\ and comments.
c. Director. Central Terminal Operations (AJT-C). Re,·iews SRM document. indicating approvaJ and by signing a memorandum (requesting approval) addressed to the Director. Terminal Safety and Operations Suppo1t Office (AJT-2).
d. Terminal Safety and Operations Support Office. The Terminal Airspace and Procedures Group (AJT-22) will re,·ie'' and indicate concw-rence through signature prior to fon,arding to the
Director. I erminal Safe~· and Operations Suppon Office ( AJT-2) for apprO\al signature (see exan1plc lnuial High Risk signature page at Appendix.
~See ATO S\1S \lanual. Chap 3: Safct) Risk Management. for risk te..el definitions and detenmnaLion process - A TO is required ro obtain AO\ appro"al for mtrigations ofimuall~ 1dentified high-risk hazards 1 HRH). For '-AS chango tmolving initial tugb nsk. Facility Dismct Offices should noti~ the Safe~ Assurance Group ( AJV-C I) The Safet!- Assurance Group \\ill coordinate v.ith Term mal Airspace and Procedures Group ( AJT-28) for AOV concurrence at predetermined phases during the RM process. Offices should refer to Safet: Oversight Ci rcular~ {SOC) 07-02 and 07-05 for additional guidance on imual HRHs.
c - l
JC 723?..15 09 1 30'2008 ,\ppendix C
e. afc~ \lanagement System'Safe~· Risk \lanagemem Office (AJS-2). The Director. ATO
S~tS SR..\.1 Office (AJS-2) re,iews the SR...\1 documenL indicating concurrence through signature on the appro\'alline.
f Air Traffic Safety Q\·ersight (AOV). All high risk hazard mitigation(s) must be approved b) AOV prior 10 implementing a change to the NAS. The Director. Air Traffic Safct) Oversight (AOV 1) indicates approval of initial high risk mitigation(s) by providing a Mitigation Approml Signature on the SRMD Signature Page.
g. Vice PresidenL Terminal Services (AJT-0). Initial high risk(s) that has/ha\ e been mitigated to medium or lo"'. can onl: be accepted at the Vice President le' el.
2. ~ledium/Lon- Risks - SR!\tD Risk Acceptance \\ill be ''ithin the FacilityDistrict ~·tanager le,el ho,,e,·er, the SR\fD appro\.·aJ must also be obtained from the Central Terminal Director and re,·iev.· by the Central Sef\.·ice Center for re\'iew and concurrence prior to implementation ofthe proposed change. The Central Service Center. Operational Support Group (OSG). Safe~ ....\ssurance Group (SAG). and in select cases the Planning a Requirements Group (PRG) are required to review the SRMDs. monitor and track mitigation ofall medium risk hazards throughout the lifecycle ofthe change or Lmtil risk is mitigated to low.
a. Terminal Facility'District Manager. fhe lnitiating Terminal Facilit) ,,;11 coordinatelroute through the District Office. The District Office S~\1POC ·will review and then \\.ill coordinate/route to the Central Operations Support Group ( OSG ). Af\·-C?.. Ifthe District Office is the initiator. then the District Oilice will coordinate route through the OSG.
b. Operations Suppon Group (AJV-(2). The OSG \\ill re' ie\\ the S~1 documents from a technical perspectiYe and fof\.Yard to the Safet) Assurance Group(. AG). AIY-Cl. The SAG v.ill re,·ie\' the documents from a Safety Risk 'Y1anagcment proc:es~ perspectiYe and i rnecessary. provide comments and/or recommendations to OSG. OSG \Viii combine SAG comments and/or recommendations with their own and provide a consolidated response to the Facility/District Office. The SAG and OSG member reviewing the SRM document will indicate by signing they have reviewed and are in concurrence with the contents. SR,\1 processes, and format ofthe document. SRMDs which meet requirements established in the ATO SY1S Manual \\ill be forwarded for approval to the Director. Central ferm.inal Operations. Should the change require in\Ol\'ernent b) the
Planning and Requirements Group (PRG). the SR.\ID ,,;JIbe coordinated routed to the PRG for their reYiew and comments.
c. Director. Central Terminal Operations lAJT-C). Re,iews SR~l document indicating apprm·aJ and by signing and anaching a memorandwn (requesting appro\'al) addressed to the Director. Terminal Safet) and Operations Suppon Office (AJT-2).
Facility/District Manager. Facility/District Manager accepts medium and 1o"'v risk(s) resulting fi·om terminal airspace and procedural changes (see example Medium/J,ow Risk Ha:=ard\ signature page at Appendix F.
( - 2
JC 7232.15 09 3012008 Appendix C
3. Medium/Low Risks: ~ew \Vaiver Requests that do not affect separation minima- New waivers are those waivers that constitute the tirst ofa kind or when the location or equipment is changed or modified. or resubmissions of waivers for a specified period oftime (e.g .. Fly-Ins. Air Shows. etc). SRMDs associated with requests for wah·ers that do not affect separation minima must be coordinated and routed through the :follO\\ing ofl}ces:
a. ferminal Facility District Manager. The Terminal initiating Facili~ \\ill coordinate/route through the District Office. The District Ollice SR...\1 POC \\il l review and then will coordinate/route to the Central Operations Support Group (OSG). AJV-C2. lf thc District Office is the initiator. then the District Office will coordinate/route through the OSG.
b. Operations Suppon Group (OSG). AJ\"-C2. The OSG '"ill revie'' the SR\.1 documents from a technical perspecti,·e and forward to the . afet) Assurance Group (SAG). AJY-CL The SAG ''ill
review the documents from a afety Risk t-.1anagemem process pcrspecth e and if necessary. provide commentS and/or recommendations to OSG. OSG v.ill combine SAG comments and/or
recommendations with their 0\\11 and provide a consolidated response to the Facility/District Office. The SAG and OSG member reviewing the SRM document will indicate by signing they have
re\ iewed and are in concurrence with the contents. SR.\ I processes. and format ofthe document. SR..\IDs which meet requirements established in the ATO S~1S Manual \\ill be forwarded for approval to the Director. Central Terminal Operations. Should the change require in'oh cment b~
the Planning and Requirements Group (PRG), the SR>.ID v.ill be coordinated romed to the PRG for their review and comments.
c. Director, Central Tenninal Operations (AJT-C). Reviews Waiver Request along with SRM document. and indicates appro,·al and by signing a memorandum (request for approval) addressed to
the Director. Terminal Safety and Operations Support Office (AJT-2).
d. Tenninal Safet) and Operations Suppon Oftice. The Terminal Airspace and Procedures Group (A.JT-22) '"ill revie'' the SRMD and indicate concurrence (through signature) prior to forwarding to the Director. Tenninal Safety and Operations Support Office (AJT-2). Upon approval by AJT-2. new \vaivcrs that do not affect separation minima may be implememed b) the initiating Facility/District \\ithout further approval b} A TO-S. TI1e Director. Terminal Safety and Operations Suppon Office (AJT-2) \\ill apprme/disapprO\·e the \\aivenia memorandtun. to the Director. Central I"crrninal Operations (AJ r-C)
e. Facility/District \.1anager. Facility/District ~fanager accepts meditun lo'v risk(s) resulting from new waivers to tenninal airspace and procedures which do not affect separation mini ma (see example Medium/Low Risk: l'lew Waiver Requests nor affecting Separation .\finima signature page at Appendix G).
-t. 'tedium/Low Risks: ~ew \"\ ah er Requests affecting separation minima - :\e'' waivers affecting separation minima \\ill require A rO-S as ,._ell as AOV approYal R..\IDs associated ''"ith requests lor waivers affectjng separation minima must be coordinated v..ith the folJO\\ing offices:
Tenninal vacilitytDistrict Manager. The Initiating Facility will coordinate/route through the Dist1ict Oilice. TI1e District Ollice SR.Ivr POC will rcvie'" and then will coordinate/route to the Central
c - 3
JC 7232.15 09/30/2008 Appendix C
Operations Support Group ( OSG ). AN-C2. If the District Office is the initiator. then the District Office ''ill coordinate roure through the Operations uppon Group (OSG).
a Operations Suppon Group (OSG). AJ\'-C2. The OSG ''ill re\ie'' the S~\1 documents from a technical perspective and lon,ard to the Safet) . \sstrrance Group (SAG) . ..-V\'-C 1. The SAG ''ill
re' ie" the documents from a atety Risk.\ lanagement process perspective and ifneccssaJ). provide comments and/or recommendations to OSG. OSG ,,;n combine SAG comments and or recommendations "'ith their O\\TI and provide a consolidated response to the facili~ District Office.
l he SAG and OSG member re\iev.ing the SR.Jv1 document '"ill indicate b~ signing they have reviewed and are in concurrence with the contents. R.\1 processes. and torrnat ofthe document. Should the change require involvement by the Planning and Requirements Group (PRG). the SRJ\riD
will be coordinated/routed to the PRG for their revie\\ and comments. SRMDs \vtlich meet requirements established in the A TO SMS Manual \\ill be forvvarded 1or approval to the Director, Central Terminal Operations. Should the change require involvement by the Planning and
Requirements Group tPRG). the SRMD will be coordinated/routed to the PRG lor their review and comments.
b. Director. Central Terminal Operations ( AJT-C). Re' ie·w SRM document and indicates apprmal and b~ signing a memorandum (request for apprm al) addressed to the Director. Terminal
afet) and Operations Support Office (AJT-2).
c. T emrinal Safety and Operations Suppon Office. The T enninal Airspace and Procedures Group (AJT-22) ,,;n re' ie" the SR..'viD and indicate concurrence (dlfough signature) prior to
ton\'a:rding to the Director. I em1inal Safet) and Operations Support Office (AJT-2) for signature.
d. Safety '.\tfanagement ~stem/Safet) Risk .\tanagement Office (.-\JS-2). The Director. A TO :V1S SR1v1 Office (AJS-2) reviews the SRM document and indicates appro,·al b) signing the apprm al line. ATS-2 will coordinate and submit the waiver request to AOV for review.
e. Air Traffic Safety Oversight Office. Air Traffic afety Oversight (AOV) indicates approval of new waivers affecting separation minima by forwarding a memorandum stating consent. The SRM document is returned to A TO-S for routing back to the Facility/District Ofllce.
f Facility/District.\1anager. Facility!Oistrict t-.lanager accepts medium1.0\\ risk(s) resulting !Tom new waivers to tenninal airspace and procedures affecting separation minima (see example .\ledium Low Risk. XeH H'ail·er RequesiS .~!feeling Separation .\finima signature page at Appendix I f).
5. :\>1edinm/Lml Risks: \\ ah er Renewals not affecting cparation ~linima - Existing ,..,aivers are those waivers in effect prior w }.1arcb 14th. :wo5 and accepted by AOV as being pan ofthe NAS baseline. SR.vlDs <bisociated "ith requests for wai\er renewals not affecting separation minima must be coordinated "ith the follo"i.ng offices:
a Terminal Facili~ Dbt.rict Manager. The Initiating Facility will coordinate route through the District Oftlce. The District Office SRM POC will re' ie'' and then ':viii coordinate route to the
c -4
JC 7232.15 09/30/2008 Appendix C
Central Operations Support Group (OSG), AJV -C2. If the District Office is the initiator, then the District Office will coordinate/route through the Operations Support Group (OSG).
b. Operations Support Group (AJV-C2). The OSG will review the SRM documents from a technical perspective and forward to the Safety Assurance Group (SAG). AJV -C 1. The SAG \\-ill review the documents from a Safety Risk Management process perspective and ifnecessary, provide comments and/or recommendations to OSG. OSG will combine SAG comments and/or recommendations with their own and provide a consolidated response to the Facility/District Office. The SAG and OSG member reviewing the SRM document will indicate by signing they have reviewed and are in concurrence with the contents. SRM processes. and format ofthe document. Should the change require involvement by the Planning and Requirements Group (PRG ), the SRMD \vill be coordinated/routed to the PRG for their review and comments. SRMDs which meet requirements established in the ATO SMS Manual vvill be forwarded for approval to the Director, Central Tenninal Operations. Should the change require involvement by the Planning and Requirements Group (PRG). the SRMD will be coordinated/routed to the PRO for their review and comments.
c. Director, Cenn·al Termjnal Operations (AJT -C). Reviews the SRM documentation and inilicates approval and by signing a memorandum (request for waiver renewal) addressed to the Director, Terminal Safety and Operations Support Office (AJT-2).
d. Terminal Safety and Operations Support Office. The Terminal Airspace and Procedures Group (A.TT-22) review the v~:aiver renewal SRMD and indicate concurrence (through signature) prior to fornrard:ing to the Director. Terminal Safety and Operations Support Office (AJT-2) for signature. Upon approval by AJT-2. waiver renewals not affecting separation minima may be in1plemented by the initiating Facility/District without firrther approval by ATO-S or AOV. The Director, Tenninal Safety and Operations Support Office (AJT-2) will approve/ilisapprove the waiver renewal via memorandum, to the Director, Central Tenninal Operations (AfT-C).
e. Facility/District Manager. Facility/District Manager accepts medium/low risk(s) resulting from renewal of waivers to terminal airspace and procedures which do not affect separation minima (see example Medium/Low Risk: Waiver Renewal Requests not Affecting Separation Minima signature page at Appenilix I).
6. Medium/Low Risks: Waiver Renewals that affect separation minima- Renewals to existing separation minima waivers require ATO-S approval and AOV acceptance. SRMDs associated with requests for renewal ofseparation minimal waivers must be coordinated with the following offices:
a Tenninal Facility/District Manager. The Initiating Facility will coordinate/route through the District Office. The District Office SRM POC will review and then will coordinate/route to the Central Operations Support Group (OSG), AJV-C2. Jfthe District Office is the initiator, then the
Disnict Office will coordinate/route through the Operations Support Group (OSG).
b. Operations Support Group (AJV-C2). The OSG will review the SR.M documents from a technical perspective and forward to the Safety Assurance Group (SAG). AJV-Cl. The SAG will review the documents from a Safety Risk Management process perspective and ifnecessary, provide
c -5
JC 7232.15 09 30,2008 Appendix C
comments and/or recommendations to OSG. OSG \\ill combine SAG comments and/or
recommendations \\ith their O\\U and pro,ide a consolidated response to the Facilit) District Office. The SAG and 0 G member re\ie"ing the SR~1 document will indicate b~ signing the~ have re\·iewed and are in concurrence ~ith the contems, SR..t\1 processes. and format ofthe document. Should the change require involvement by the Planning and Requirements Group (PRG). the SRMD \\ill be coordinated/routed to the PRG for their re,iew and comments. SR.\1Ds which meet requirements established in the ATO s·Ms \1anual v.ill be forwarded for approvaJ to the Director. Central Terminal Operations. Should the change require in,·olvement b~ the Planning and Requirements Group (PRG). the SRMD \Viii be coordinated'routed to the PRG for their revie~ and comments.
c. Director, Central Terminal Operations(. VT-C). Re,ie\\S wai,er SR..\l document and indicates approval and b~ signing a memorandum (request for approval) addressed to the Director. Terminal Salet)· and Operations Support Office (A.IT-2).
d. TcrminaJ afety and Operations Support Office. 1l1e Terminal Airspace and Procedures Group (AIT-22) ''ill re\ie\\ the waiver SR-\ID and indicate concurrence (through signature) prior to forwarding to the Director. TerminaJ Safer:· and Operations Suppon Office (AIT-2) for signature.
e. Safety Management System/Safety Risk Management Office. The Manager, Safety Risk Management Group (AJS-:22) will review the waiver SR.t\11 document and indicate concurrence by forwarding to the Director ..\TO S~1S/SRM Office UVS-2) for approval and signature. AJS-2 \\ill coordinate and submit the wah·er request through A TOto AOV for acceptance.
f. Air Traffic Safety Oversight Office. The Air Trailic Safety Oversight Office (J\OV) accepts renewals to existing separation minima waivers5• hO\\·evcr. an AOV Accepumce Signarure is not required on the SR~ID Signature Page. "lbe SR.\ I document is returned to ATO-S for routing back to the faciJi~ District Office . .-\0\" ,,;n initiate a separate memorandum. signed indicating concurrence or non-concwTence lor lhe request.
Facility/District Manager. Facility/District Manager accepts medium/low risk(s) resulting from renewals to existing separation minima ·waivers (see example .\1edium Lo" Risk Wah·er Renewals -{(tec:ting )eparativn \finima signature page at Appendix J ).
7. Mediu m/Low Ri ks as a result ofan IG. NTSB. AOV inquiry or High Visibilit) item. The SRMD should be coordinated v.ith the follov.ing offices:
a. Terminal Facility District vfanager. The Initiating Facility ·will coordinate route through the District 01Ticc. The District Office SRM POC v.ill re\icv. and then '1.iU coordinate route to the Central Operations Suppon Group (OSG). AJV-C2. Ifthe District Office is the initiator. then the Distiict Office v.-ill coordinate/route through the Operations Support Group (OSG).
b. OperatioQ.l) Suppon Group (AJV-C2). The OSG \\ill re\iewtbe S~\1 documents !Tom a reclmical perspective and forward ro the Safer:· Assurance Group (SAG). AJV-C I. The SAG "'ill
5 A.OV A fO-S Memorandum of -\greement dated Jun 8:11. 2005
c -6
JC 7232.15 09 130 2008 Appendix C
re,·iew the documents from a Safet) Risk Management process perspective and ifnecessary. pro,·ide comments and or recommendations to OSG. OSG \\ill combine SAG comments and or recommendations ''itb their O\\TI and pro" ide a consolidated response to the facilit) District Oftice. The SAG and OSG member re\iewing the SR.v1 document v.ill indicate by signing the) have reviewed and are in concurrence with the contents. SRM processes, and format ofthe document.
Should the change require invol\'ement by the Planning and Requirements Group (PRG). the SRMD
\~ill be coordinated routed to the PRG tor their review and comments. SR.\IDs which meet requirements established in the ATO S11 'v1anual \\.ill be forwarded for approval to the Director. Central Terminal Operations. Should the change require invol-vement b) the Planning and Requirements Group (PRG), t:be SRMD will be coordinated/routed to the PRG for their review and comments.
c. Director. Central Terminal Operations (AJT -C). Reviev..s waiver ~1 document and indicates approval and by signing a memorandum (request for approval) addressed to the Director. Tetminal Safety and Operations Support Office (AJT-2).
d. Terminal at~ and Operations upport Office. The Terminal Airspace and Procedures Group (All-22) ,,;11 re,·icv. the waiYer SR\ID and indicate concurrence (through signature) prior to forwarding to the Director. Tem1inaJ Safet) and Operations Suppon Office (AJT-2) for signature.
e. Safety Management System/Saiety Risk Management 011ice. The l\·1anager. Safety Risk
~1anagemenl Group (AJS-22),\ill reYie\\ the waher SRM document and indicate concurrence b) forwarding to the Director. -\TO 'MS/SR.\1 Office (AJS-2) for approval and signarure. AJS-2 "'ill coordinate and submit the ,,ai,er request to ATO-S tor acceptance.
f Air Traffic Satery 0Yersight (AOV). The Satery Management System/Safety Risk
~1anagemcnl Office (ATO- ) "ill determine "'nether the SR.\1D requires coordination \\ith AOY.
g. Air Traffic Sate!) Oversight Office (AO\'). The Air Traffic Safer~ 0\ersight Ofilce (AO\') accepts renewals to existing separation minima waiYers6 • however, an AOV Acceptance Signature is not required on the SRlviD Signature Page. The SRI\ 1 document is returned to A TO-S for routing back to the Facility/District Oftice. AOV '"ill initiate a separate memorandum. signed indicating concurrence or non-concurrence for the request.
1\ote: High visibilit) items include Land and llold Shon Operations (LAHSO). Simultaneous Convergent Instrument Approaches (SCIA). Taxi Into Position and Hold (TIPH). Simultaneous Dual'Triple/Quadruple Instrument Landing (lLS) -\pproaches. etc.
8. RMD Signature Levels. The following signatures should be included on the SR1\1.D signature page and while additional review/approval signature lines may be provided. these represent the minimum required signatures tor documentation ofhigh. medium. or lo'' risk hazards.
c. 1\0V ATO-S Memorandum of Agreement dated Jun 8'". 2005
JC 7232.15 09,3012008 Appendix C
Tem1inal signatures presume the other ATO Sen ice Cnits are not required signatories. In the eYent the other Sen-ice Cn.its or other Lines ofBusiness are required for signarure. Lheir appropriate requircments/Directi\'es must also apply as necessary.
Signatures required on the R.MD are dependent upon le,·el ofrisk identified (See appendices 1:. through J for Signarure Page examples):
a. High Initial Risk (Applicable for any SRMD with initial high risk). See Figure C-1 for a Dowchrut depicting required signature levels for High LnitiaJ Risk.
( l ) Re\ iewed by: District Safety Risk Management Focal (SRtv1 POCl Terminal Facility Manager or TemtinaJ District upport Staff Manager Central Service Center Operations Support Group {AJV-C2) Central Senice Center Safe~ Assurance Group (.-\.TV-C 1)
ferminal Airspace and Procedures Group (AJT-22)
rcrminal Safety Group (AJT-28)
(2) ApproYed bY: Director. Terminal Operations. Central Senice Area (AJT-C) Director. Tenninal Safety and Operations Support (AJT-2) Director. Safety Risk Management and Safety Management System (AJS-2)
(3) Risk Accepted b': Vice President. Terminal SeJVices (AJT-0)
b. Medium ILOl\ Risk (SRMD not associated n ith a llaiYer reque t). See Figure C-2 for a no,,·chart depicting required signature levels for ~ledium Low Risk.
( I ) ReYiewed b\: Central Service Center Operations Support Group (AIC-C2) Central Service Center Satery Assurance Group (.-\1\'-Cl)
(') Appro,·cd by: Terminal facility Manager or Terminal District Support Staff Manager
(3) Risk Accepted b': District vlanager (see "\oteJ
Note: At the discretion of the District Manager. the Facility Manager has the authority to accept risk associated with ~ledium'Low Risk SR.vlDs. \\ben the facilit) Manager accepts risk. the SRMD
must be appro,·ed by a trained SR.\1 Focal assigned ro the fu.cility \\here the change is initiated.
c. Medium /L O\~ Risk (SRMD associated with a wai-ver request not affecting separation minima). See Figure C-3 for a flov;chart depicting required signature levels for ~1edium!Low Risk associated \\lth wai\·crs not affecting separation minima
c- 8
JC 7232.15 09 30 2008 Appendix C
( 1) Re\ie\\ed b\: District Safel) Risk \lanagcment Focal (SR.,'-1 POC) Terminal Facilit) Manager or Tenninal DiS1rict Suppon taff~1anager Central Service Center Operations Support Group (AJV-C2) Central Service Center Safety Assurance Group (AJV-C1) Terminal Airspace & Procedures Group {AJT-22)
(>) Appro\·ed b\: Director, Temlinal Safet) and Operations Support (AJT-2)
(3) Risk Accepted b\: Facility District\ tanager
d. Medium /Low Risk (SRMD associated with a waiver request affecting separation minima). See Figure C-4 for a flowchart depicting required signature levels for Medium/Low Risk associated \\ith waivers alTccting separation minima
(l} Re-vie\\ ed b\: Disrrict Safety Risk Management Focal (SRM POC) Terminal Facility Manager or Terminal District Support Staff Manager Central Service Center Operations Suppon Group (AJY-C2) Central Sen·ice Center Satery Assurance Group ( \1\·-C 1 ) Terminal Airspace & Procedures Group (AJT-22)
(2) Approved b": Director. Terminal Safel) and Operations Suppon (AJT-2) Director. Safel)· Risk ~1anagement and Safety ~1anagement System (A.JS-2)
(3) Risk Accepted bv: District Manager
c. Y1edium I Low Risk (IG, ~"'TSB , AOY inqnil) or High Visibility items). See Figure C -5 tor a flowchart depicting required signature levels for ~1edium/Lov.. Risk associared \vith IG. NTSB. AOV inquiry or High \\sibility items.
(1) Reviewed b' : Districl Safery Risk \1anagement Focal (SR.i\f POC) Central Sen'ice Center Operarions upport Group (AJV-C2) Central Service Center Safety A..ssurance Group (AJV-C 1) Tenninal Airspace & Procedures Group (AJT-22)
(i) ApprO\ed bv: Tem1inal Facility Manager or Terminal District Suppon Staffyfanager
Director. TeTminal Safety and Operations Support Office (AJT-2)
09130/2008 AppendixC .JC 7232.15
Din..-ctor. ;v1anagemcnt S~stem Safety Risk vlanagemcnt Otlicc (AJS-2)
(3) Risk Acccptt.>d b' : District \tanager
c - 10
JC 7232.15 09 '30/2008 Appendix C
Initial High Risk SRMD Process
Terminal F acility/Oistrict
Manager
I
I SRMD Review
CSC Operations Support Tenninal Group (AJV-C2), Safety Airspace & Assurance Group (AJV-C1), Procedures Group Area Director (AJT-22)
SRMD Approval
Director. Satcry Risk Director, Terminal Safety & Management and Safety Operations upport (.t\JT-2) 'v1anagemem Systern
(AJS-2)
Mitigation Approval
Director, Air Traffic Safety
0\·ersigbt (AOY-1)
Risk Acceptance
Vice President T enninal
SerYices (A.IT-0)
I
Figure C-1: Initial High Risk SRMD Process
C - 11
JC 7232.15 09 '30 2008 Appendix C
J Medium/Low Risk SRMD Process
SRMD Review
SRMD Approval
T enninal Facility/District
Manager
CSC Operations Support
Group (AJV-C2). Safety Assurance Group (AJV-C1 )
Facilil) \tgr 'SR.\1 Focal
Risk Acceptance
Tenninal Facility/District
Manager
Figure C-2: Medium/Low Risk SR.\1D Process
c - 12
JC 7232.15 OQ 3012008
-\ppendix C
Mediutn/Low Risk SRMD Process (Waiver affecting separation minima)
Terminal F acility/Oistrict
Manager
SR'1D Review
CSC Operations Support Tetminal Airspace & Group (AJV-C2), Safety ~ Proced ures Group (AJT-22) Assurance Group (AJV-C1 ),
Area Director
SRVID Approval
Director. T em1inal Safety & Director. Safety Risk Operations Support (AJT-2) Management and Safety Management System (AJS-2)
Risk Acceptanee
Terminal F acility/Oistrict
Manager
Figure C-3: Medium/Lo~ Risk SRMD Process (wah'er affecting separation minima)
c- 13
.IC 7232.15 09130/2008 AppendiA C
Mediu111/Low Risk SRMD Process (Associated with waiver not affecting separation minima)
Tenninal Facility/D1stnct
Manager
SRMD Review I
CSC Operations Support
Group (AJV-C2), Safety Assurance Group (AJV-C1),
Area Director
1cm1inal Airspace & f---+ Procedures Group ( AJT-22)
SRMD Approval
Risk Accepta nee
Director. T ermmal Safet: & Operations Suppon (.\JT-2)
Tenninal Facility/District
Manager
figure C-': :\'ledium/Low Risk SRMD Proces as ociated \\ith \\aher not affecting separation minima)
c- 14
JC 7232.15 09 30/2008 Appendix C
Mediu111/Low Risk SRMD Process (IG* NTSB* AOVInquiry or High Visibility Items)
Terminal F acility/Oistrict
Manager
SRMD Review
CSC Operations Support Terminal Airspace & Procedures Group (AN-C2), Safety ---+ Group (AJT-22) Assurance Group (AJV-C1),
Area Director
SRMD Approval
Director. Terminal Safety & Director. Safe!) Risk
Operations Support (AJT-2) Management and Safe!) \lanagement System (AJS-2)
Risk Accepta nee
Terminal Facility/District
Manager
Figure C-5: Medium/Low Risk SRMD Process (IG, .:'JTSB, AOV Lnquiry or High Visibility Items)
c- 15
JC 7232.15 09/30/2008 AppendixD
Appendix D - Safety Risk Management Central Service Center (CSC) Roles and Responsibilities
The Operations Support (OSG) and Safety Assurance (SAG) Groups Support the Directors of Operation to ensure changes to the NAS comply with the SMS Manual and SRM orders and policies. In certain instances the Planning and Requirements Group will also have a major active role with Tenninal changes. The SAG specifically suppmts Safety Risk Management (SRM) and Safety Management System (SMS) activities. The SAG assists field offices by providing:
Appendix D - Safety Risk Management Central Service Center (CSC) Roles and Responsibilities
• Clarification ofSMS/SRM requirements • Assistance with SRM Docmnentation • Assistance with establishing SRM Panels • SRM Panel Jacilitation and document preparation • Assistance vvith tracking and monitoring of hazards and risk mitigation plans
All proposed changes to the NAS require SRM evaluation prior to implementation. The process below defines Service Center roles and responsibilities. and describes routing ofSRM documentation through the Central Service Center:
1. The organizational entity that generates any changes to the NAS such as new procedures. airspace changes, waivers. or changes to air traffic control and navigation systems, must submit those requested changes. along with SRM documentation. to the CSC Operations Support Group (OSG). The OSG Team Manager (AJ0-1 C) will forward the docwnent to the appropriate Support Specialist. To ensme the Service Center operates a') ··one" organization, receiving and processing SRM documents, and providing consolidated responses to the facilities/districts. the OSG will be the entry and exit point for all terminal airspace and/or procedural changes.
2. The assigned OSG Support Specialist reviews all SR.M docwuentation from a technical perspective. enswing compliance with current air traffic control policies and procedures (i.e., FAA JO
7110.65, FAA JO 72l0.3, etc) and, in cases involving waivers, adequate justification and rationale.
3. The OSG Support Specialist forwards a copy ofthe SRM document to the SAG via the Organization Evaluations Team Manager (AN-Cl). The Team Manager will assign the SRM document to the appropriate Specialist. SRM docwnents will be tracked in the Service Area Action Tracking System (SAATS).
4. Upon receipt. the SAG Specialist vvill review SRM documentation .fi-om a risk management process perspective to ensure adherence to the current SMS Manual and all applicable SMS/SRM orders. policies. and procedures. The SAG Specialist will provide any conunents or recommendations regarding the SRM document directly to the Operations Support Specialist who will cDmbine these comments with theirs·. and prepare a consolidated response to the facility/district office. lfthe OSG does not have any comments and requests the SAG Specialist to do so. the SAG Specialist may consult directly with U1e customer to resolve SRM issues. Tf necessary, the SAG Specialist could also provide a consolidated response to the cu~iomer.lithe Safety Assurance Group concurs with the
JC 7232.15 09/30/2008 Appendix I)
SR..\ I documentation. the SAG Specialist v.ill coordinate \\ith the Operations Support Spec1alist and sign d1e SR..'MD docwnent signifying Safety Assurance's review and concurrence.
5. The Operations Support Group maintains oYerall rt.."Sponsibili~ for processing ofchanges to the NAS. By serving as the primal) entry exit point tor SRv1 documents. the Director of fenninaJ Operations can be certain that , ...~hen the OSG recommends an SRM document for approval, both th~ Operations Support and Safety Assurance Groups concur ""ith the proposed change. Once approved b) the Director. the OSG ,,;11 forward SR-\f documentation to the appropriate Headquaners offices and copy the SAG.
6. The Safety Assurance Group will ensure that all ha.Lards associated with SR..MD. shave been entered into the Hazard Tracking System. Ifthey haYe not. the AG v~ill coordinate "ith the initiator ofthe change and enter the hazards. The SAG ,,;11 track risk mitigation strategies implemented by the
Facility/District Offices and work with the initiator of the change to assure all S\1S responsibilities are met.
For an) questions regarding safe{) risk management or the S~lS process. please contact the Safet) Assurance Group Organizational Evaluations Team at (817) 222-4503. For Operations Support assistance. contact (817) 222-5530.
D- 2
9130 08 JC 7232.15 \ppendi.'{ E
Appcndh E Signatur-e Page for Initial High Risk Hazards (example)
Title: '\arne'fitlc of<)R\10 associated \\ith initial High Risk I la?.ard
Initiator: XYZ Facilit) District \1anag.er (rna~ be a upport :vtanager or Initiator's Organization: XYZ Terminal Faciti~ District Initiator's Phone \umber:
ubmi ion Date: R\lD Version \umber:
~R\10 Version Date:
pecialist)
Tenninal District Oftic~ ate~ Risk \Ianagemem hx..<il Date
Ienninal Facilit) ~tanager or Terminal District Ollice Date
Dec:;ignce. Cenn·al Sen icc Center Date Safct: Assurance Group
\J\'-C l
Designee. Central Sen ice Center Operations Support ·pccialist t\JV-C2
Date
Designee. Terminal A-irspace and Procedures Group
\JT-22
Date
Designee. Tenninal Sate{) Group Date \JT-28
R..\1D Approval Signature(s):
- \ trs. '\:anc) B. Kon. Dtrector. Date I enninal OperatiOn.!>. Central Sen ice Area
\\ htle additional rc' ic'' appro\ a s gnatures rna~ be included. thi!> e\ample repn!,enb the minimum required
<>ignarure tor initial htgh rbk haLard~
E- l
JC 7232.15 09130/2008 -\ppendix E
AJT-C
\1r. Raul C. Tre\ino. Director. Dati! l emlinaJ Salct~ and Operations Support Office
\.11-:!
\1r. lluan '\gu)t!n. D1rt!Ctor. Date . afct) Risk \1anagement and Safe~ "Y1anagemem ~~stems
-\JS-2
Risk Acceptance Signature:
\ 1r. Bruce Johnson. Y 1ce President. Date Terminal Sen ict.>s. \J T-0
[ - 2
9/30/08 JC 7232.1 5 Appendix F
Appeodnf Signature Page for Yfedium!Low Risk Hazards (example)8
Title: l'ame.'Title of R..\.fD associated \\lth ~fediwn Lo\>o Risk Hazard
Initiator: XYZ Facilit: District ~lanager (ma~ be a upport Manager or pecialist) Initiator's Organization: }...)'"Z Tenninal Facility District Initiator's Phone Number: Submission Date: SR,lD Version ~umber: SRMD Version Date:
SR'\-ID Re"ie'' ed b~:
Tenninal District Oftice Safety Risk Management Focal Dare
rerminal Facility Manager or T enninal District Date Support StaJf Manager
Designee. Central Sen ice Center Date Safet) Assurance Group AJ\'-Cl
Designee. Central Sen·ice Center Date Operations Support Specialist Al\'-C2
SRMD Approval Signature(s):
~trs. Nancy B. Kort. Director. Date renninal Operations. Central Ser\ ice Area
\JT-C
Risk Acceptance Signature:
T emlinal District \'tanager Date
'While addttional rc\te\\ approval ~ignature lines rna~ be included. thiS example repre<>ents the minimum required stgnatures for medium IO\\ nsk hazards
F- I
JC 7232.15 09/30/2008 Appendix E
Airpon 1raflic Control TO\\er Tem1inal Radar -\pproach Control (ATCTTRACO~ ) [see noteI
9 30 08 J( 7~3~.15 <\ppendix G
-\ppendi~ G Signature Page for \ledium!Lo" Risk: '\en Waiver Requests not affecting separation minima (e~mpl e)"
T itle: 1\jamc I itle of. R.\ID associated \\ith \Vai\er Request Initiator: XY L l atilit; District \fanager (ma) be a · upport \lanager or Initiator's Organi.J.ation: ~1'L Terminal Facilit: Di-rnct In itiator's Phone ~umb er : Submission Date:
RMD Version "iumber : SRMD Version Date:
pecialist)
SR\1D Reviewed b):
Tcnninal District Office Safer: Risk. ~fanagcrnem FocaJ Date
Tem1inal Facilit) \tanager or TenninaJ District Date Support StaffManagcr
De'igncc. Centr..tl ~t!n ice Center Date
Safet~ \ssurance Crroup AI\"-Cl
Designee. Central Sen ice Center Operations Support SpeciaJist AJV-C2
Date
Destgnee. Tenninal Atrspace and Procedures Group
o\JT-2~
Date
Designee. Tenninal 'afct; Group
<\JT-~8
Date
Q While additional re\ 1\!\\ appro\al -.ignarures may be mcluded. thi-. c\ample represents the minimum required signatures for mcd low risl-. wai\'er requests not affecung separatitm minima
G- 1
JC 7232.15 09 30/2008 \ppendix G
• R\ID Appro' al Signature(s):
\ h">. '\anc~ B. Kon. Dira.t x.
Icnnmal Opcratiol'b. Cemral enice Area
\JT-C
Date
\1r. Raul Trevino. D1rector.
1cnninal Safet) and Operations Support Office AJT-2
Risk Acceptance Signature:
Date
I t!nninal District \ 1anager Date \1rpon Traffic Control ·1 O\\Cr I cnninal Radar .\pproach Control (ATCTTR.\CO"\) [see note]
G- 2
9 30 '08 JC 7232.15 Appendix H
AppendixH Signature Page for ;\ledium/Lo"\\ Risk: :\'en Wah er Requests Affecting Separation 'linima (example)1"
Title: Name/Title ofSRMD associated with Wai\'er Request Initiator: XYZ Facility'District Manager (may be a Support Manager or Specialist) Initiator's Organization: XYZ TemlinaJ facili~ District Initiator's Phone :'\umber: Submission Date: SRMD Version Number: SRI\IID Version Date:
SR.'ID Revie'" ed by:
T enninaJ District Office atety Risk Managemem Focal Date
TemlinaJ Facilit) ~tanager or Tem1inaJ District Date Support Staff Manager
Designee. Central er\ice Center Date Safety Assurance Group AN-Cl
Designee. Central er\ice Center Operations Support Specialist
AN-C2
Date
Designee. 1 erminaJ Airspace and Procedures Group A..IT-22
Date
Designee. ferminal Safer: Group Date .-\JT-28
10 While additional revie'v\ 'approval signatures may be included. this example represents the minimum required signarures formed lo\\ risk \\aher requesrs affecting ~eparation minima
H- 1
JC 7232.15 0930/2008 Appendix H
R\ID Approl'al Signature(s):
~1rs. ~ancy B. Kon. Director. Date T emlinal Operations. C enrral enice Area A.IT-C
Mr. Raul C. Tre\.ino. Director. Date Tenninal Safety and Operations Supp011 Office
A.J 1'-2
Mr. Huan Nguyen. Director. Date Satety Risk Management and Safety Management Systems. AJS-2
Risk Acceptance Signature:
Tem1inal District \ fanager Date -\irpon T.ra.fiic Control Tower Tem1inal Radar Approach Control (ATCTTR.-\CO>-) [see note]
"\Ote: At the cliscretion ofthe District :Manager. !.he facility \1fanager has the aulhori~ lO accept risk
associated \vith Med1um Low risk SRMDs.
II - 2
9 30108 JC 7232.15 Appendixl
Appendix I
Appendix I
ignature Page for Medium!Lo" Risk: Waiver Rene"als ~ot Affecting Separation :\:linima {example)11
Title: i\ame'Title of. ~1D associated ,,;th Request tor Waiver Renewal
Lnitiator: XYZ Facili~ Disnict Manager (ma~ be a upport .Manager or Specialist) Initiator's Organization: XYZ Terminal Facilit) District Initiator's Phone Number: Submission Date:
R\-ID Version :\umber: R"\ID Version Date:
RMD Reviewed b~ :
Terminal District Office Safe[) Risk Management Focal Date
Terminal Facilit)· \Ianager or Terminal District Date upport Staff ~1anager
Designee. Central Service Center Date
ate~ Assurance Group AJV-Cl
Designee. Central Ser.ice Center Operations Suppon Specialist A.TV-C2
Date
Designee. T emrinal . \irspace and Procedures Group AJ r-22
Date
Designee. Terminal afet: Group Date AJT-28
11 While additional re' ie\\ appro\ al signatures ma) be included. this e\amplc represents me minimum required s1gnarures for med.lO\\ risk wai\er rene\\als not affecting separation minima
1- 1
JC 7232.15 09 30,2008 Appendix l
SRMD Approval Signature(s):
\ frs. ~anc) B. Kon. Director. Date Tenninal Operations. Central Sen·ice Area Office. AJT -C
Nf.r. Raul C. Tre\ ino. Director. Date T enninal Safe~ and Operations upport Office AJT-2
Risk Acceptance Signature:
Terminal District \-tanager Date Airport Traffic Control Tower, Tenninal Radar Approach Conn·ol (ATCT!TR.ACON) [see notej
I-~
9 30108 JC 7232. l5 Appendix J
.-\ppendL\: .J ~ Signature Pagt> for ~Iedium/Low Risk: Waiver Rene\\ als Affecting Separation ):linima (example)'
Title: Nameffitle ofSRJ\..ID associated vvith Request for Waiver Rene,-va.l Initiator: XYZ Facility/District Manager (may be a Support Manager or Specialist)
Initiator's Organization: XYZ Tenninal Facility/District Initiator's Phone Number: Submission Date: SR\ID Re\ision Number:
R\ID Revision Date:
SR\JD Reviewed by:
Terminal District Office Safet) Risk Management Focal Date
Terminal f acility Manager or Terminal District Date Support StaiTManager
Designee. Central Sen-ice Center Dare Satety Assurance Group AJY-Cl
Designee. Central SerYice Center Operations Support Specialist AN-C2
Date
Designee. Tenninal Airspace and Procedures Group AJT-22
Date
Designee. T enninaJ Safe~ Group Date AJT-28
~ ·while additional re\ie\\ approHI signarnres rna} be mcluded. this example represenrs the mintmum required signatures formed IO\\ risk \\al\er rcne,,als affecting separauon miruma
J- I
JC - :G2.15 09 302008 , \ppendi.x J
~R:\-ID Approval Sigoature(s):
~lr.:,. ~anc) B. Kon. Director. Tenninal Opc!ration.-.. Central en ice Area Office. \.1 1 -C
Oat~
Mr. Raul C. Trevino. Director.
fcnninal Salct) and Operations Support Ofiice . .\J I -2
Date
\ 1r. Huan Nguyen. On-ector. Date: Safety Risk Management and Safety Management Systems. A.JS-2
Rhk Acceptance 'ignature:
renninal District \tanager Date \upon Trallic Control I ower 1 cnninal Radar Approach Control (ATCTrrRACO'\) [sec note]
J - 2
9 30.08 JC 7232.15 Appendix K
Appendix K -Definition and Acronyms
Appendix K -Definition and Acronyms
DEFINITIO~S
a. Approval. The formal act ofresponding favorably to a change submitted by a requesting
organization. This action is required prior to the proposed change being implemented.
b. Concurrence. Agreement ''ith results or conclusiofu expressed in a change justification.
SR~IDM. SR\10. or other docwnem.
c. Hazard. Any real or potential condition that can cause injw-y. mness. or death to people; damage
to or loss ofa system. equipment or property: or damage to the environment. A condition that is a prerequisite to an accident or incident.
d. ~AS. The ~ational Airspace System is the collection ofdocuments. personnel. procedures.
systems. and sen·ices that the A TO uses to provide A TC and navigation sen ices.
e. Oversight. To validate the development ofa defmed system and verilY compliance to a pre
defined set ofstandards: Regulatory upervision.
f. Requirement. An essential attribute or characteristic ofas~ stem. It is a condition or capability that must be met or passed by a system to satisl) a contract. standard. specification. or other
formally imposed document or need.
g. Risk. The composite of predicted se\erity and likelihood ofthe potential effect ofa hazard in the
\\Orst credible s~ stem state.
h. Safe{). Freedom from unacceptable risk.
i. Safety Directive. A mandate from AOV to the A TO to take immediate corrective action to
address a non-compliance issue that creates a significant unsafe condition. as determined by AOV.
j. a fet) Management y tern (S~lS). An integrated collection ofprocesses. procedures. policies. and programs that are used to assess. define. and manage the safety risk in the provision ofA TC and navigation service~.
k Safety Risk Management (SRM). A formalized. proactive approach to system safe~. SRM is a methodology applied to all ~A changes that ensures that hazards are identified and unacceptable risk is mitigated prior to the change being made. It provides a framework to ensure that once a change is made. i1 continues to be tracked throughout its lifecycle.
I. Safety Risk Management Decision Memo (S.Ri\1DM). The documentation ofthe decision U1at
the proposed change does not impact NAS safety. The memo includes a \\Titten statement ofthe decision and supporting argument and is signed by the manager and kept on tile fur a period equi\'alenL to the lifecycle ofthe system or change.
m. Safety Risk Management Document (SRJ\tlD). Thoroughly describes the safety analysis fbr a
given proposed change. It documents the e\idence to support whether or not the proposed change to the system is acceptable from a safet) risk perspecti,·e. SR.\•tDs are kept and maintained b~ the organization responsible for the change lor a period equi,·alem to the litecycle ofthe system or change.
K - 1
JC 7232.15 09 30'2008 -\ppendix K
n. System. An integrated set ofconstituent pieces that are combined in an operational or support
environment to accomplish a defined objecth·e. These pieces include people. equipment, information. procedures. facilities, services. and other supp011 services.
ACROI'1rvMS
AO\"
~\TC
ADf ATO ATO-S A TO-T CBI CMl:.L CTS1\
ADf ATO ATO-S A TO-T CBI CMl:.L CTS1\
eL~lS FA-\
HRH HTS lCAO IG ILS
KS L\lTSO
~AS
~ISB OSG
PRG SAO SClA SME S\1S
SR~1 SR.\.1DM SR\ID TrPH
Air Traffic Safet) Oversight erqce Air Traffic Control Air Traffic ~tanager Air T raftlc Organi7..ation Air Traffic Organization Safet~ \t1anagemem System (SMS) Office Air Traffic Organization Temlinal Computer Based Instruction Center for Management Excellence and Learning Central Terminal Service Area Elecrronic Learning ~1anagemem System Federal Aviation -\d.rninistrntion Iligh Risk Hazard !Iazard Tracking System International Civil Aviation Organi7.ation Inspector General Instrument Landing System Knowledge Sharing Netw·ork Land and Hold Short Operations
SR~1 SR.\.1DM SR\ID TrPH
~ational Airspace System '-ationa! Transportation Safe~ Board
Operations Suppon Group Programs and Requirements Group Safety Assurance Group Simultaneous Convergent Instrument Approaches Subject Matter Expert Safe{) ~anagement System Safe{) Risk ~ lanagement SR.\f Decision \ tcmo
R..\1 Document Ta"\i in ro Position and Hold
K- 2