37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1269168 |
Time | |
Date | 201506 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Stearman |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | Direct Visual Approach |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Multiengine Flight Crew Rotorcraft Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 25 Flight Crew Total 6005 Flight Crew Type 195 |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural FAR |
Narrative:
I planned to fly from ZZZ1 to ZZZ2. I had a passenger who is a friend recovering from prostate surgery. On takeoff I found that it was choppy so I spoke to my passenger on the intercom and we agreed it was not a good idea to fly 50 miles each way in the bumpy conditions because of his recent surgery. I called lancaster ATC and asked for a left turn to head south east for a much shorter flight to airport ZZZ for lunch. ZZZ1 ATC approved the request and no further communication was received from them. I flew the route using dead reckoning as it was a familiar route to me. At about 7NM from ZZZ I changed to the CTAF and at about 5NM I announced I was inbound to ZZZ from the west. I checked the AWOS and the wind favored runway xy. I announced left downwind to runway xy and finals to land. No contact was made to me at any time by anyone at ZZZ. I landed; parked; and chocked the aircraft. At that time a woman from the FBO came up and asked me to call TRACON by telephone. I did so and was informed I had entered a tfr centered on wilmington. I was asked for my details and I gave the information as requested. A few minutes later the secret service called me and asked for my full details which I supplied. I received two further calls from the secret service and was asked to remain at ZZZ pending an interview and I did so. Agent X and one other interviewed me and I answered all their questions. I consented to my stearman being searched and photographed. I have reconstructed in my mind what happened and I have identified the error. I used foreflight and adds (aviation digital data service) for flight planning; weather; and tfrs. I entered my route in foreflight and there were no tfrs on the planned route. I have an e-mail conforming the entry from foreflight. I changed my destination in flight and headed in an easterly direction unaware that there was a tfr which covered airport ZZZ. I was over 20 miles from the center; in the outer ring; and did not cause any air traffic issues or hazard. I did not file a flight plan and I did not call enroute. It was my error; I researched the route but because I had not anticipated flying in the opposite direction I did not research the route I ended up taking. I did not use foreflight for navigation itself. I will not rely on foreflight for briefing in future and will obtain a briefing including a 360 degree overview to cover the possibility of a change in route. I had not considered this eventuality before when flight planning as we invariably ask for a briefing on the intended route of flight.
Original NASA ASRS Text
Title: Pilot on a VFR flight changed planned destination enroute inadvertently penetrating a TFR; resulting in an airspace security breach.
Narrative: I planned to fly from ZZZ1 to ZZZ2. I had a passenger who is a friend recovering from prostate surgery. On takeoff I found that it was choppy so I spoke to my passenger on the intercom and we agreed it was not a good idea to fly 50 miles each way in the bumpy conditions because of his recent surgery. I called Lancaster ATC and asked for a left turn to head south east for a much shorter flight to Airport ZZZ for lunch. ZZZ1 ATC approved the request and no further communication was received from them. I flew the route using dead reckoning as it was a familiar route to me. At about 7NM from ZZZ I changed to the CTAF and at about 5NM I announced I was inbound to ZZZ from the West. I checked the AWOS and the wind favored runway XY. I announced left downwind to RWY XY and finals to land. No contact was made to me at any time by anyone at ZZZ. I landed; parked; and chocked the aircraft. At that time a woman from the FBO came up and asked me to call TRACON by telephone. I did so and was informed I had entered a TFR centered on Wilmington. I was asked for my details and I gave the information as requested. A few minutes later the Secret Service called me and asked for my full details which I supplied. I received two further calls from the Secret Service and was asked to remain at ZZZ pending an interview and I did so. Agent X and one other interviewed me and I answered all their questions. I consented to my Stearman being searched and photographed. I have reconstructed in my mind what happened and I have identified the error. I used Foreflight and ADDS (Aviation Digital Data Service) for flight planning; weather; and TFRs. I entered my route in Foreflight and there were no TFRs on the planned route. I have an e-mail conforming the entry from Foreflight. I changed my destination in flight and headed in an easterly direction unaware that there was a TFR which covered Airport ZZZ. I was over 20 miles from the center; in the outer ring; and did not cause any air traffic issues or hazard. I did not file a flight plan and I did not call enroute. It was my error; I researched the route but because I had not anticipated flying in the opposite direction I did not research the route I ended up taking. I did not use Foreflight for navigation itself. I will not rely on Foreflight for briefing in future and will obtain a briefing including a 360 degree overview to cover the possibility of a change in route. I had not considered this eventuality before when flight planning as we invariably ask for a briefing on the intended route of flight.
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.