37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1004278 |
Time | |
Date | 201204 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Aircraft 1 | |
Make Model Name | MD-83 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Critical Deviation - Procedural Published Material / Policy Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor |
Narrative:
I was working the R14/R88 position when I accepted two radar hand offs from approach; the MD83 departing to the northwest and the B737; approximately 10 miles in trail; departing to the northeast. The MD83 declared an emergency requesting to turn back to the airport. I cleared the MD83 to amend climb to 100 and cleared direct to the airport. I also asked nature of emergency and if they would need assistance. The MD83 explained that there was an electric odor in the cockpit and no assistance needed. I then called approach on the land line and asked to have them stop the B737 at 090 and explained the emergency. They had already shipped the aircraft and gave me control. The B737 was actually checking in on the loud speaker as I was talking to approach. I hung up on approach and gave the B737 an 'immediate clearance to climb to 160 and turn to a 090 degree heading for emergency traffic. Both aircraft at this time were maybe 3-4 miles apart and reacting to TCAS alerts. The MD83 to climb and the B737 to descend; after the TCAS alert the B737 began its climb and back on course and the MD83 I gave further instruction from approach to return to the field; where the MD83 landed without incident. This was a mistake on my part. I gave the MD83 the clearance back to approach without positive separation with the B737; believing I could coordinate with approach to stop the B737 before separation would be lost. I was wrong. I would recommend that I not make a hasty reaction to an emergency aircraft before a complete scan of traffic.
Original NASA ASRS Text
Title: Enroute Controller described a TCAS RA event involving two Air Carrier departures; the first declaring an emergency and requesting an immediate return to the departure airport; separation was not insured with the following aircraft.
Narrative: I was working the R14/R88 position when I accepted two RADAR hand offs from Approach; the MD83 departing to the northwest and the B737; approximately 10 miles in trail; departing to the northeast. The MD83 declared an emergency requesting to turn back to the airport. I cleared the MD83 to amend climb to 100 and cleared direct to the airport. I also asked nature of emergency and if they would need assistance. The MD83 explained that there was an electric odor in the cockpit and no assistance needed. I then called Approach on the land line and asked to have them stop the B737 at 090 and explained the emergency. They had already shipped the aircraft and gave me control. The B737 was actually checking in on the loud speaker as I was talking to Approach. I hung up on Approach and gave the B737 an 'immediate clearance to climb to 160 and turn to a 090 degree heading for emergency traffic. Both aircraft at this time were maybe 3-4 miles apart and reacting to TCAS Alerts. The MD83 to climb and the B737 to descend; after the TCAS alert the B737 began its climb and back on course and the MD83 I gave further instruction from Approach to return to the field; where the MD83 landed without incident. This was a mistake on my part. I gave the MD83 the clearance back to Approach without positive separation with the B737; believing I could coordinate with Approach to stop the B737 before separation would be lost. I was wrong. I would recommend that I not make a hasty reaction to an emergency aircraft before a complete scan of traffic.
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.