 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A center trainee controller reported an aircraft deviating for weather lost an engine and had to divert.
| Attributes | |
| ACN | 1494855 |
| Time | |
| Date | 201711 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.ARTCC |
| State Reference | US |
| Environment | |
| Flight Conditions | Marginal |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Aircraft Equipment Problem Critical Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Inflight Event / Encounter Weather / Turbulence |
Narrative:
I was receiving on the job training (OJT) on combined sectors and had just recently taken position. I was displaying weather information from FL330 and above. The first few minutes on position I had been coordinating weather deviations with pilots and adjacent sectors. I was on the line getting a ride report at FL380 well out ahead of an aircraft on my frequency that was getting a lousy ride at FL380 when I received a call on override from another sector. The sector was requesting to hand off aircraft X climbing to FL390 which was not per SOP which I approved. Aircraft X checked on climbing to FL390 on course which skirted along the northern edge of the weather and asked if I knew what rides were like ahead as he had been in moderate turbulence the last 10 minutes.I provided him with the information I had to his east at FL380 of intermittent light turbulence. Aircraft X advised that he was going to need to deviate left of course. I coordinated this deviation with adjacent sectors who quickly approved it. Aircraft X advised he was getting moderate to severe turbulence and his new course was completely clear of my depicted weather so I started filling out a paper PIREP form at which point aircraft X began to descend. I questioned his descent and aircraft X advised that he was an emergency and was in a descent and that he had also lost an engine.aircraft X had conflicting traffic at FL350 so I asked aircraft X to maintain FL360 if able while I coordinated with other sectors. I coordinated the emergency descent information to the next sector who approved my request. Aircraft X when asked intentions advised he would like to divert to [nearby airport] so I provided a clearance with FL350 as an altitude to maintain and shipped the aircraft to the next sector. I feel like I did all I could to assist aircraft X as he checked on a course that he had requested. I coordinated his deviations and provided him with any relevant information I had on the weather at the time which was very limited due to time on position and no aircraft traveling along his route previously.perhaps upgraded weather information would allow controllers to be more aware of weather in their sector. Lots of controllers here talk about how nice it would be to have weather and radar processor (warp) weather which I'm unfamiliar with.
Original NASA ASRS Text
Title: A Center trainee Controller reported an aircraft deviating for weather lost an engine and had to divert.
Narrative: I was receiving On the Job Training (OJT) on combined sectors and had just recently taken position. I was displaying weather information from FL330 and above. The first few minutes on position I had been coordinating weather deviations with pilots and adjacent sectors. I was on the line getting a ride report at FL380 well out ahead of an aircraft on my frequency that was getting a lousy ride at FL380 when I received a call on override from another sector. The sector was requesting to hand off Aircraft X climbing to FL390 which was not per SOP which I approved. Aircraft X checked on climbing to FL390 on course which skirted along the northern edge of the weather and asked if I knew what rides were like ahead as he had been in moderate turbulence the last 10 minutes.I provided him with the information I had to his east at FL380 of intermittent light turbulence. Aircraft X advised that he was going to need to deviate left of course. I coordinated this deviation with adjacent sectors who quickly approved it. Aircraft X advised he was getting moderate to severe turbulence and his new course was completely clear of my depicted weather so I started filling out a paper PIREP form at which point Aircraft X began to descend. I questioned his descent and Aircraft X advised that he was an emergency and was in a descent and that he had also lost an engine.Aircraft X had conflicting traffic at FL350 so I asked Aircraft X to maintain FL360 if able while I coordinated with other sectors. I coordinated the emergency descent information to the next sector who approved my request. Aircraft X when asked intentions advised he would like to divert to [nearby airport] so I provided a clearance with FL350 as an altitude to maintain and shipped the aircraft to the next sector. I feel like I did all I could to assist Aircraft X as he checked on a course that he had requested. I coordinated his deviations and provided him with any relevant information I had on the weather at the time which was very limited due to time on position and no aircraft traveling along his route previously.Perhaps upgraded weather information would allow controllers to be more aware of weather in their sector. Lots of controllers here talk about how nice it would be to have Weather and Radar Processor (WARP) weather which I'm unfamiliar with.
Data retrieved from NASA's ASRS site 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.