37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1662151 |
Time | |
Date | 201907 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZOB.ARTCC |
State Reference | OH |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | EMB ERJ 145 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
I received a hand-off on aircraft X at FL200 from ZNY phillipsburg sector. There was a wall of heavy and mostly extreme precipitation directly ahead of aircraft X that stretched north to south for approximately 80 miles. Aircraft X checked on my frequency requesting an immediate climb and left deviation for the weather. FL200 was in the data block as a hard altitude so I was unaware of any higher requested altitude. So I asked the pilot what his requested altitude was and he responded with FL340. I approved a left deviation and a climb to FL230 (which was my sector's ceiling) and flashed for higher to bki sector. The pilot then told me that the previous controller from ZNY would not approve any higher altitude or weather deviation and the pilot stated that the previous controller put him in a dangerous situation. I called psb sector and asked for control on aircraft X and other aircraft in trail with the same situation happening again. The controller stated that he had no traffic and they were my control. Aircraft X requested a phone number to speak with ZNY management over the incident because of the danger he was out in. Laziness from the ZNY controller not putting in a higher requested altitude and not approving higher or deviations to aircraft for weather is extremely careless and unsafe to the flying public. That controller; in my opinion; should receive disciplinary action and recurrent training.
Original NASA ASRS Text
Title: ZOB Center Controller reported that an aircraft had requested deviations and higher altitude to avoid severe weather which were not approved by the previous Center Controller.
Narrative: I received a hand-off on Aircraft X at FL200 from ZNY Phillipsburg sector. There was a wall of heavy and mostly extreme precipitation directly ahead of Aircraft X that stretched north to south for approximately 80 miles. Aircraft X checked on my frequency requesting an immediate climb and left deviation for the weather. FL200 was in the data block as a hard altitude so I was unaware of any higher requested altitude. So I asked the pilot what his requested altitude was and he responded with FL340. I approved a left deviation and a climb to FL230 (which was my sector's ceiling) and flashed for higher to BKI sector. The pilot then told me that the previous Controller from ZNY would not approve any higher altitude or weather deviation and the pilot stated that the previous Controller put him in a dangerous situation. I called PSB sector and asked for control on Aircraft X and other aircraft in trail with the same situation happening again. The Controller stated that he had no traffic and they were my control. Aircraft X requested a phone number to speak with ZNY management over the incident because of the danger he was out in. Laziness from the ZNY Controller not putting in a higher requested altitude and not approving higher or deviations to aircraft for weather is extremely careless and unsafe to the flying public. That Controller; in my opinion; should receive disciplinary action and recurrent training.
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.