 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A pilot failed to cancel his IFR flight plan after landing because he was overwhelmed by unexpected airport special event operations. Reporter suggested the IFR flight plan cancellation procedure should be simplified.
| Attributes | |
| ACN | 1380068 |
| Time | |
| Date | 201608 |
| 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 | Small Aircraft Low Wing 1 Eng Fixed Gear |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Taxi |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Private |
| Experience | Flight Crew Last 90 Days 75 Flight Crew Total 1150 Flight Crew Type 150 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural FAR |
Narrative:
Enroute to my filed destination on IFR flight plan. Visual conditions. I did not cancel my IFR in the air with the controller. Once on the ground I had an extended taxi to the ramp due to a special event with multiple taxiways closed and; part of the ramp closed and difficulty finding a parking spot due to the special event. This delayed canceling my flight plan.contributing factors:1) no aerodrome NOTAM for the special event. A NOTAM would have alerted me that this small airport would have been congested.2) unable to receive AWOS until 7 miles from airport. This was the first notice that I had of a special event. The AWOS information included a very lengthy list of areas of the airport that were closed. I'm curious as to whether there is a problem with the AWOS transmitter because one is generally able to receive the AWOS/ASOS etc. From at least 30 miles at most airports. I would be in favor of a better way to cancel IFR flight plans at small airports as the aircraft exits the runway.
Original NASA ASRS Text
Title: A pilot failed to cancel his IFR flight plan after landing because he was overwhelmed by unexpected airport special event operations. Reporter suggested the IFR flight plan cancellation procedure should be simplified.
Narrative: Enroute to my filed destination on IFR flight plan. Visual Conditions. I did not cancel my IFR in the air with the controller. Once on the ground I had an extended taxi to the ramp due to a special event with multiple taxiways closed and; part of the ramp closed and difficulty finding a parking spot due to the special event. This delayed canceling my flight plan.Contributing factors:1) No aerodrome NOTAM for the special event. A NOTAM would have alerted me that this small airport would have been congested.2) Unable to receive AWOS until 7 miles from airport. This was the first notice that I had of a special event. The AWOS information included a very lengthy list of areas of the airport that were closed. I'm curious as to whether there is a problem with the AWOS transmitter because one is generally able to receive the AWOS/ASOS etc. from at least 30 miles at most airports. I would be in favor of a better way to cancel IFR flight plans at small airports as the aircraft exits the runway.
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.