37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 633931 |
Time | |
Date | 200410 |
Day | Wed |
Place | |
Locale Reference | navaid : oed.vortac |
State Reference | OR |
Altitude | msl single value : 10500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zse.artcc |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | VFR |
Aircraft 2 | |
Controlling Facilities | artcc : zse.artcc |
Operator | other |
Make Model Name | Fighting Falcon F16 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Experience | flight time last 90 days : 44.6 flight time total : 272.8 flight time type : 113.4 |
ASRS Report | 633931 |
Person 2 | |
Affiliation | government : military |
Function | flight crew : single pilot |
Events | |
Anomaly | airspace violation : entry non adherence : far non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | FAA Airspace Structure Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
While cruising on VFR flight plan around a tfr, I incorrectly centered the 30 NM tfr radios at the oed VOR (medford) instead of the 10.2 NM point on the oed 175 degree radial. This mistake put me 5 NM inside the tfr. An F16 flying patrol crossed my flight path telling me something was wrong. I immediately tuned ZSE and was told of my position and given a heading to exit the tfr airspace, which I expedited. I was surprised to find I was inside the prohibited airspace that I took such planning to avoid. The mistake on my part was not insisting the FSS briefer to slowly repeat the details of the tfr and its exactly location. Definitely, a lesson learned. Here is what I'd do in hindsight: upon receiving information about a tfr that would require a sizeable deviation from original flight plan, I'd go somewhere else, or do it on another day. Ask the briefer at FSS to repeat and/or clarify tfr specifics. Filed an IFR flight plan to make routing/radar vectoring around the tfr more assured.
Original NASA ASRS Text
Title: C172 PENETRATES AN OREGON TFR WHEN THE PLT MIS-LOCATES THE CTR OF THE TFR AT THE OED VOR VICE 10 MI S AS NOTAMED. IS INTERCEPTED BY F16.
Narrative: WHILE CRUISING ON VFR FLT PLAN AROUND A TFR, I INCORRECTLY CTRED THE 30 NM TFR RADIOS AT THE OED VOR (MEDFORD) INSTEAD OF THE 10.2 NM POINT ON THE OED 175 DEG RADIAL. THIS MISTAKE PUT ME 5 NM INSIDE THE TFR. AN F16 FLYING PATROL CROSSED MY FLT PATH TELLING ME SOMETHING WAS WRONG. I IMMEDIATELY TUNED ZSE AND WAS TOLD OF MY POS AND GIVEN A HDG TO EXIT THE TFR AIRSPACE, WHICH I EXPEDITED. I WAS SURPRISED TO FIND I WAS INSIDE THE PROHIBITED AIRSPACE THAT I TOOK SUCH PLANNING TO AVOID. THE MISTAKE ON MY PART WAS NOT INSISTING THE FSS BRIEFER TO SLOWLY REPEAT THE DETAILS OF THE TFR AND ITS EXACTLY LOCATION. DEFINITELY, A LESSON LEARNED. HERE IS WHAT I'D DO IN HINDSIGHT: UPON RECEIVING INFO ABOUT A TFR THAT WOULD REQUIRE A SIZEABLE DEV FROM ORIGINAL FLT PLAN, I'D GO SOMEWHERE ELSE, OR DO IT ON ANOTHER DAY. ASK THE BRIEFER AT FSS TO REPEAT AND/OR CLARIFY TFR SPECIFICS. FILED AN IFR FLT PLAN TO MAKE ROUTING/RADAR VECTORING AROUND THE TFR MORE ASSURED.
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.