37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 552812 |
Time | |
Date | 200207 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | special use airspace : zzz.restricted |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : zzz.tracon |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 36.3 flight time total : 458 flight time type : 388 |
ASRS Report | 552812 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | airspace violation : entry non adherence : far non adherence : published procedure other anomaly other |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | other |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airspace Structure ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Departed ZZZ for ZZZ1. Route of flight using GPS was ZZZ direct ZZZ2 direct ZZZ3 direct ZZZ1. It was my understanding that a straight line between ZZZ2 and ZZZ3 below 2500 ft will keep an aircraft clear of the ZZZ tfr and the class B airspace. I have used this route several times this yr on trips to the eastern shore of maryland with no problems encountered. Upon landing at ZZZ1, I was instructed to call a government representative. I also received a call from ZZZ TRACON. I was surprised to learn that a course between ZZZ2 and ZZZ3 would clip the edge of the tfr. I was told that I had penetrated the tfr by as much as 4 mi. I was not using radar services but was monitoring ZZZ2 approach on one radio and the unicom frequencys of ZZZ2 and ZZZ3 on the second radio. I honestly felt that I was clear of the ZZZ tfr, but have been informed by 3 different agencies that I was not. As a result, I will not pass between these 2 areas without first establishing 2-WAY communication, receiving a discrete transponder code, and specific vectors from ATC before flying east of ZZZ2.
Original NASA ASRS Text
Title: GA PLT PENETRATES TFR.
Narrative: DEPARTED ZZZ FOR ZZZ1. RTE OF FLT USING GPS WAS ZZZ DIRECT ZZZ2 DIRECT ZZZ3 DIRECT ZZZ1. IT WAS MY UNDERSTANDING THAT A STRAIGHT LINE BTWN ZZZ2 AND ZZZ3 BELOW 2500 FT WILL KEEP AN ACFT CLR OF THE ZZZ TFR AND THE CLASS B AIRSPACE. I HAVE USED THIS RTE SEVERAL TIMES THIS YR ON TRIPS TO THE EASTERN SHORE OF MARYLAND WITH NO PROBS ENCOUNTERED. UPON LNDG AT ZZZ1, I WAS INSTRUCTED TO CALL A GOV REPRESENTATIVE. I ALSO RECEIVED A CALL FROM ZZZ TRACON. I WAS SURPRISED TO LEARN THAT A COURSE BTWN ZZZ2 AND ZZZ3 WOULD CLIP THE EDGE OF THE TFR. I WAS TOLD THAT I HAD PENETRATED THE TFR BY AS MUCH AS 4 MI. I WAS NOT USING RADAR SVCS BUT WAS MONITORING ZZZ2 APCH ON ONE RADIO AND THE UNICOM FREQS OF ZZZ2 AND ZZZ3 ON THE SECOND RADIO. I HONESTLY FELT THAT I WAS CLR OF THE ZZZ TFR, BUT HAVE BEEN INFORMED BY 3 DIFFERENT AGENCIES THAT I WAS NOT. AS A RESULT, I WILL NOT PASS BTWN THESE 2 AREAS WITHOUT FIRST ESTABLISHING 2-WAY COM, RECEIVING A DISCRETE XPONDER CODE, AND SPECIFIC VECTORS FROM ATC BEFORE FLYING E OF ZZZ2.
Data retrieved from NASA's ASRS site as of July 2007 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.