37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1551244 |
Time | |
Date | 201806 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | TPA.Airport |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR DEAKK FIVE |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
[On] DEAKK5 arrival; I was pilot monitoring and first officer (first officer). Captain was pilot flying. Descending around the deakk intersection; we asked for 'direct guzda' for building thunderstorms. The controller did not clear us to guzda. However; he approved deviations right of course for weather; and never told us a fix to fly towards after clear of the weather. Still deviating for weather; when we were abeam jstrm; the captain turned heading 360 to parallel the arrival course and avoid building weather over guzda. The controller asked us what our heading was; to which I responded '360 for weather'. He said he didn't clear us that far right (although he never specified a limit for deviations) and to turn 20 degrees left and to maintain 5;000 feet. The captain turned 20 degrees left; but saw that it would put us very close to the building weather. We asked for a lower altitude; to which the controller denied our request and said that there was no weather. He only cleared us to 5;000 feet. We knew it was not extreme weather; but wanted to avoid it anyway. Unfortunately; the controller's sense of urgency and lack of cooperation had us penetrate through the building cloud. We experienced light to moderate turbulence; and our vsi momentarily increased to +700 FPM (during a descent). We felt that whatever the controller was so upset about was more important to safety than a few bumps that we would've preferred to avoid by offsetting and paralleling the course for a few more miles. Within a few minutes; the weather that the controller said 'did not exist' turned into a thunderstorm.we are all professionals and should act as such. For this controller to question our honesty about avoiding weather; in florida in the summer; is unprofessional. I understand that controllers have very busy and stressful jobs; but the captain and I were trying to also do our jobs and keep the aircraft; crew; and passengers as safe as possible. It would have been more helpful for the controller to communicate with us what he needed so we could develop another plan of action for weather avoidance.in the future; when getting weather deviations approaching a turning point on a route; I will ask for clarification on which fix to fly to after deviations are completed. I will also do my best to point out exactly which weather we are referring to (request deviations for weather at 1 o'clock and 30 miles).
Original NASA ASRS Text
Title: A319 First Officer reported TPA Approach Controller denied requests for weather deviation resulting in an encounter with turbulence.
Narrative: [On] DEAKK5 arrival; I was Pilot Monitoring and FO (First Officer). Captain was Pilot Flying. Descending around the DEAKK intersection; we asked for 'direct GUZDA' for building thunderstorms. The controller did not clear us to GUZDA. However; he approved deviations right of course for weather; and never told us a fix to fly towards after clear of the weather. Still deviating for weather; when we were abeam JSTRM; the Captain turned heading 360 to parallel the arrival course and avoid building weather over GUZDA. The controller asked us what our heading was; to which I responded '360 for weather'. He said he didn't clear us that far right (although he never specified a limit for deviations) and to turn 20 degrees left and to maintain 5;000 feet. The captain turned 20 degrees left; but saw that it would put us very close to the building weather. We asked for a lower altitude; to which the controller denied our request and said that there was no weather. He only cleared us to 5;000 feet. We knew it was not extreme weather; but wanted to avoid it anyway. Unfortunately; the controller's sense of urgency and lack of cooperation had us penetrate through the building cloud. We experienced light to moderate turbulence; and our VSI momentarily increased to +700 FPM (during a descent). We felt that whatever the controller was so upset about was more important to safety than a few bumps that we would've preferred to avoid by offsetting and paralleling the course for a few more miles. Within a few minutes; the weather that the controller said 'did not exist' turned into a thunderstorm.We are all professionals and should act as such. For this controller to question our honesty about avoiding weather; in Florida in the summer; is unprofessional. I understand that controllers have very busy and stressful jobs; but the captain and I were trying to also do our jobs and keep the aircraft; crew; and passengers as safe as possible. It would have been more helpful for the controller to communicate with us what he needed so we could develop another plan of action for weather avoidance.In the future; when getting weather deviations approaching a turning point on a route; I will ask for clarification on which fix to fly to after deviations are completed. I will also do my best to point out exactly which weather we are referring to (request deviations for weather at 1 o'clock and 30 Miles).
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.