37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1063783 |
Time | |
Date | 201301 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | P180 Avanti |
Flight Phase | Final Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter Fuel Issue Inflight Event / Encounter Weather / Turbulence |
Narrative:
During the event; I was providing OJT for a cpc-it on local south. The weather had been varying between MVFR and IFR throughout the morning because of a storm system moving through. Low ceilings and low visibility are rare in ZZZ which causes a lot of unnecessary paranoia amongst management and other controllers who have never worked at a facility that experiences bad weather. Earlier in the shift; the flm had already ordered us to stop all divergent turns that we have prearranged with TRACON in the LOA; and to provide 7 mit on any jet traffic following turboprop or prop traffic. At the time; we were operating simultaneous dependent ILS approaches between runway 8 and runway 7. The flmic ordered the local controllers to enforce the 2-mile stagger on final; even though he had already told TRACON that we were not seeing any traffic until they were near the ILS approach minimums. This was also against the TRACON-ZZZ LOA. According to the LOA: ZZZ must: assume separation responsibility for radar arrivals on the same or adjacent final approach within 3NM of the landing threshold. At any time; ZZZ cannot provide visual separation; the ZZZ flmic/controller in charge must advise the TRACON flmic/controller in charge and the radar controller must assume separation responsibility. In the event I'm reporting; air carrier X was on final for runway 7; 2.3 miles in front of air carrier Y on final for runway 8. Air carrier X was at approximately a 1.5 mile final when the flm ordered us to send air carrier X around because of the overtake from air carrier Y on the runway 8 final. We sent air carrier X around; unbeknownst to us; the TRACON finals' controller responsible for runway 8 had already initiated a go around with air carrier Y. Air carrier X replied to our go around transmission with 'unable; minimum fuel.' for safety's sake; I told the trainee to re-clear him to land and told the flm to have air carrier Y go around because air carrier X had minimal fuel and would be landing. We then observed air carrier Y start a climb for the go around. Had air carrier X completed his go around as instructed; there would have been an instant loss of separation and some sort of divergent turn would have been required. Following the incident; the flm came over and told us that just because air carrier X says 'minimum fuel' and not 'emergency fuel'; it doesn't make him an emergency. I feel as though his argument is pure semantics. To question an aircraft on a precision approach short final in IFR weather as to whether or not they meant to say they are on emergency fuel is as much a safety hazard as two aircraft less than 3 miles apart in IFR weather. I would recommend that the ZZZ flmic review the ZZZ/TRACON LOA section regarding separation on approaches during periods of low visibility.
Original NASA ASRS Text
Title: Tower Controller described a potential multiple go around event during marginal weather when staggered separation was in doubt and one aircraft declared minimum fuel; the reporter questioning the FLM's LOA knowledge.
Narrative: During the event; I was providing OJT for a CPC-IT on Local South. The weather had been varying between MVFR and IFR throughout the morning because of a storm system moving through. Low ceilings and low visibility are rare in ZZZ which causes a lot of unnecessary paranoia amongst management and other controllers who have never worked at a facility that experiences bad weather. Earlier in the shift; the FLM had already ordered us to stop all divergent turns that we have prearranged with TRACON in the LOA; and to provide 7 MIT on any jet traffic following turboprop or prop traffic. At the time; we were operating simultaneous dependent ILS approaches between Runway 8 and Runway 7. The FLMIC ordered the Local controllers to enforce the 2-mile stagger on final; even though he had already told TRACON that we were not seeing any traffic until they were near the ILS approach minimums. This was also against the TRACON-ZZZ LOA. According to the LOA: ZZZ Must: Assume separation responsibility for RADAR arrivals on the same or adjacent final approach within 3NM of the landing threshold. At any time; ZZZ cannot provide visual separation; the ZZZ FLMIC/CIC must advise the TRACON FLMIC/CIC and the RADAR Controller must assume separation responsibility. In the event I'm reporting; Air Carrier X was on final for Runway 7; 2.3 miles in front of Air Carrier Y on final for Runway 8. Air Carrier X was at approximately a 1.5 mile final when the FLM ordered us to send Air Carrier X around because of the overtake from Air Carrier Y on the Runway 8 final. We sent Air Carrier X around; unbeknownst to us; the TRACON finals' Controller responsible for Runway 8 had already initiated a go around with Air Carrier Y. Air Carrier X replied to our go around transmission with 'Unable; minimum fuel.' For safety's sake; I told the Trainee to re-clear him to land and told the FLM to have Air Carrier Y go around because Air Carrier X had minimal fuel and would be landing. We then observed Air Carrier Y start a climb for the go around. Had Air Carrier X completed his go around as instructed; there would have been an instant loss of separation and some sort of divergent turn would have been required. Following the incident; the FLM came over and told us that just because Air Carrier X says 'minimum fuel' and not 'emergency fuel'; it doesn't make him an emergency. I feel as though his argument is pure semantics. To question an aircraft on a precision approach short final in IFR weather as to whether or not they meant to say they are on emergency fuel is as much a safety hazard as two aircraft less than 3 miles apart in IFR weather. I would recommend that the ZZZ FLMIC review the ZZZ/TRACON LOA section regarding separation on approaches during periods of low visibility.
Data retrieved from NASA's ASRS site as of July 2013 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.