 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The pilot of a single engine aircraft became confused with the multiple revisions to the temporary flight restrictions and entered a tfr.
| Attributes | |
| ACN | 1274105 |
| Time | |
| Date | 201506 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | JZI.Airport |
| State Reference | SC |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Route In Use | Direct |
| Flight Plan | None |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Commercial Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 14.3 Flight Crew Total 364 Flight Crew Type 291 |
| Events | |
| Anomaly | Airspace Violation All Types Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
My husband and I arrived at charleston executive (kjzi) and saw tfr 5/2063. Later on; [we were informed] that there had been multiple changes to the NOTAM. On the day of departure; because 5/2603 went to the bottom of list of NOTAM on [software] (second to the last; and listed in the last 7 days section) and [being informed that] the tfr being effective at noon; I got confused and took the NOTAM (5/4342) as the amendment for 5/2063. A brief was done [electronically]. An IFR plan was also filed; just in case the weather between charleston and [the destination] deteriorated en route. I placed all my attention on getting out of charleston exec before xa:30 (5/4342) and avoiding ground and mid-air collisions given the busy airspace. After a normal take-off from runway 27; I climbed to 700 feet before turning en route for a [southwest heading] for an altitude of 7;500 feet. Little did I know that I had violated 5/2063. And I was totally shocked when our airport manager told me that I should call FAA about my violation upon landing. I understand that despite the confusion; there is no excuse for me to make such a mistake as a pilot in command (PIC). I feel extremely sorry that at such a trying time for the nation given the tragedy and large work load for the FAA; that my mistake added extra work to the good people involved. I hope that the following measures could be taken to prevent future inadvertent violations for me as well as for other pilots. 1) educationfor pilots from states that multiple vips do not appear together frequently; it may be necessary to provide a vip tfr faasteam course. The frequency of changes of their schedule as well as the tfrs can be really confusing. 2) tfr notationconfusion resulted from multiple vips and multiple changes of tfr NOTAM. If there are more than one vip coming to the airspace; it will be very helpful if notations are put in to clarify that this NOTAM is different from the other and warn the pilots of potential confusion.
Original NASA ASRS Text
Title: The pilot of a single engine aircraft became confused with the multiple revisions to the Temporary Flight Restrictions and entered a TFR.
Narrative: My husband and I arrived at Charleston Executive (KJZI) and saw TFR 5/2063. Later on; [we were informed] that there had been multiple changes to the NOTAM. On the day of departure; because 5/2603 went to the bottom of list of NOTAM on [software] (second to the last; and listed in the last 7 days section) and [being informed that] the TFR being effective at noon; I got confused and took the NOTAM (5/4342) as the amendment for 5/2063. A brief was done [electronically]. An IFR plan was also filed; just in case the weather between Charleston and [the destination] deteriorated en route. I placed all my attention on getting out of Charleston Exec before XA:30 (5/4342) and avoiding ground and mid-air collisions given the busy airspace. After a normal take-off from Runway 27; I climbed to 700 feet before turning en route for a [southwest heading] for an altitude of 7;500 feet. Little did I know that I had violated 5/2063. And I was totally shocked when our airport manager told me that I should call FAA about my violation upon landing. I understand that despite the confusion; there is no excuse for me to make such a mistake as a Pilot In command (PIC). I feel extremely sorry that at such a trying time for the nation given the tragedy and large work load for the FAA; that my mistake added extra work to the good people involved. I hope that the following measures could be taken to prevent future inadvertent violations for me as well as for other pilots. 1) EducationFor pilots from states that multiple VIPs do not appear together frequently; it may be necessary to provide a VIP TFR FAASTeam course. The frequency of changes of their schedule as well as the TFRs can be really confusing. 2) TFR NotationConfusion Resulted from Multiple VIPs and multiple changes of TFR NOTAM. If there are more than one VIP coming to the airspace; it will be very helpful if notations are put in to clarify that this NOTAM is different from the other and warn the pilots of potential confusion.
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.