37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1735026 |
Time | |
Date | 202003 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | EC130 |
Operating Under FAR Part | Part 135 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | VFR |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Commercial Flight Crew Rotorcraft |
Experience | Flight Crew Last 90 Days 12 Flight Crew Total 2714 Flight Crew Type 2585 |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
I was on a scenario-based training flight with a helicopter air ambulance company. My flight path was from ZZZ to nnnnn hospital east which; required me to transition through the ZZZ1 class C surface area. I was unable to contact approach and tower via the normal frequencies. Weather at that time was; VFR; overcast; and blustery; isolated storms passing through (not reported); with winds out of the west at approximately 18 knots; gusting mid to high 20's at the surface. However; at an altitude of approximately 1;750 MSL; winds were touching the medium to high 30 knot range (if I remember correctly; the controller gave a peak wind of 33 at the surface) where we [were] experiencing light to moderate turbulence. I was aware of my close proximity to the surface area and was attempting to steer clear of it as I was trying obtain an alternate frequency (fumbling with the GPS) and make contact with approach or tower; with the added pressure that my 'imaginary patient was dying' from my instructor. However; during my juggling act and despite my efforts; unfortunately; barely crossed into the surface area prior to radio contact due to the winds pushing me into the surface area. There was no threat to any other aircraft. Nor when finally; in contact with tower; they did not mention the situation or instruct me to call the tower via phone. Request for the transition was granted without further issue. Lesson learned was not to presume that a frequency that was expected to be used and available; would be available. Check ATIS and notams prior to flight. And follow the old maxim... Aviate; navigate; and then communicate.
Original NASA ASRS Text
Title: Pilot reported being task saturated during a training flight with bad weather; resulting in an airspace violation.
Narrative: I was on a scenario-based training flight with a Helicopter Air Ambulance company. My flight path was from ZZZ to NNNNN Hospital East which; required me to transition through the ZZZ1 Class C surface area. I was unable to contact Approach and Tower via the normal frequencies. Weather at that time was; VFR; overcast; and blustery; isolated storms passing through (not reported); with winds out of the west at approximately 18 knots; gusting mid to high 20's at the surface. However; at an altitude of approximately 1;750 MSL; winds were touching the medium to high 30 knot range (if I remember correctly; the controller gave a peak wind of 33 at the surface) where we [were] experiencing light to moderate turbulence. I was aware of my close proximity to the surface area and was attempting to steer clear of it as I was trying obtain an alternate frequency (fumbling with the GPS) and make contact with Approach or Tower; with the added pressure that my 'imaginary patient was dying' from my instructor. However; during my juggling act and despite my efforts; unfortunately; barely crossed into the surface area prior to radio contact due to the winds pushing me into the surface area. There was no threat to any other aircraft. Nor when finally; in contact with Tower; they did not mention the situation or instruct me to call the Tower via phone. Request for the transition was granted without further issue. Lesson learned was not to presume that a frequency that was expected to be used and available; would be available. Check ATIS and NOTAMs prior to flight. And follow the old maxim... Aviate; Navigate; and then Communicate.
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.