37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 951900 |
Time | |
Date | 201106 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ANC.Airport |
State Reference | AK |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Cessna Stationair/Turbo Stationair 6 |
Flight Phase | Initial Climb |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Handoff / Assist |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
During this event I was training on local assist and a certification was occurring on local control. A flm and cpc were plugged in; watching the local control trainee. I had informed the local control once before about launching aircraft off of runway 25R with aircraft conducting an ILS approach to runway 14. The flm or trainer said nothing to the trainee about it. The first time was a B190 departing 25R and he barely made it through the intersection of the two runways. This time local launched a C206 with a B737 on about a 3 to 4 mile final. I again informed the local control that the B737 was on an ILS approach and they have to protect for the missed approach. This time the cessna did not make it through the intersection before the B737 crossed the threshold of runway 14. Again the flm and cpc said nothing to the trainee about this. After being relieved from position another supervisor; which was in the tower cab monitoring; told the local controller and myself that we had an oe because the cessna was not through the intersection. The local controller explained he thought he didn't have to because we have a NOTAM that makes the two runways not intersect and we land two aircraft at the same time with this NOTAM never having to protect for a go around. Additionally; approach gives us 'ties' to both runways all the time because of this NOTAM. I have filed reports about this procedure and how it makes no sense how a 'magical' NOTAM can stop two runways from intersecting. Nothing has been changed and we continue to use this unsafe practice. This is a very confusing procedure we use to bypass the regulations in the 7110.65. Obviously even the flm saw nothing wrong with this or they are required to step in and stop the operation. [My] recommendation [is to] stop using this 'magical' NOTAM as it only puts aircraft in unsafe proximity and abide by the 7110.65 for intersecting runway separation. Have approach control stagger approaches to converging/intersecting runways. Anchorage gets a complexity factor for intersecting runways so the FAA has already determined these runways in fact do intersect.
Original NASA ASRS Text
Title: ANC Controller voiced concern regarding the current NOTAM that declares that Runways 14 and 25R do not intersect; permitting operations that appear to be in conflict with FAA 7110.65 provision.
Narrative: During this event I was training on Local Assist and a certification was occurring on Local Control. A FLM and CPC were plugged in; watching the Local Control trainee. I had informed the Local Control once before about launching aircraft off of Runway 25R with aircraft conducting an ILS approach to Runway 14. The FLM or trainer said nothing to the trainee about it. The first time was a B190 departing 25R and he barely made it through the intersection of the two runways. This time Local launched a C206 with a B737 on about a 3 to 4 mile final. I again informed the Local Control that the B737 was on an ILS approach and they have to protect for the missed approach. This time the Cessna did not make it through the intersection before the B737 crossed the threshold of Runway 14. Again the FLM and CPC said nothing to the trainee about this. After being relieved from position another supervisor; which was in the Tower Cab monitoring; told the Local Controller and myself that we had an OE because the Cessna was not through the intersection. The Local Controller explained he thought he didn't have to because we have a NOTAM that makes the two runways not intersect and we land two aircraft at the same time with this NOTAM never having to protect for a go around. Additionally; Approach gives us 'ties' to both runways all the time because of this NOTAM. I have filed reports about this procedure and how it makes no sense how a 'magical' NOTAM can stop two runways from intersecting. Nothing has been changed and we continue to use this unsafe practice. This is a very confusing procedure we use to bypass the regulations in the 7110.65. Obviously even the FLM saw nothing wrong with this or they are required to step in and stop the operation. [My] recommendation [is to] stop using this 'magical' NOTAM as it only puts aircraft in unsafe proximity and abide by the 7110.65 for intersecting runway separation. Have Approach Control stagger approaches to converging/intersecting runways. Anchorage gets a complexity factor for intersecting runways so the FAA has already determined these runways in fact do intersect.
Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.