AA5 on pleasure flight enters tfr in dfw area.

Attributes
ACN	590637
Time
Date	200307
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	special use airspace : p49.prohibited
State Reference	TX
Altitude	msl bound lower : 2000 msl bound upper : 3800
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : d10.tracon
Operator	general aviation : personal
Make Model Name	Cheetah, Tiger, Traveler
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Flight Plan	None
Aircraft 2
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
ASRS Report	590637
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 other : f-16 interceptor
Resolutory Action	flight crew : exited penetrated airspace
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance FAA Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I'm enclosing a detailed description of the events. My plane busted a tfr that was only announced 2-3 hours before I took off. An F-16 intercepted me while I was returning to my home airport. I obtained a duats briefing, but did not notice the tfr as it was apparently sandwiched between the usual crawford and a new one near hou. The hou tfr was listed first. Had the tfr been listed first or with the normal airport NOTAMS, I would have seen it. Also, the personnel at the local FBO did not seem to know about it when I landed there and got gas, just mins before the intercept. The chain of events: I had lost my cell phone 2 days before and my fellow flying friends had tried to contact me to tell me about the 'last min tfr' only 30 mins before I took off. Also, I had been working a lot that week and had not watched the news. The biggest factor though was the 'hard to read' and 'poor location' of the tfr in the duats system. From now on, I will 'call' for a flight briefing. In hindsight, one thing was very surprising that you might want to know for the future. It's the fact the pilot of the F-16 never directly or indirectly addressed me in any of his communications. He never said 'plane near the lake' or my type plane, or my call sign, even though I was using them in each and every call I made to him. His lack of communication made it very confusing for me to know what he wanted me to do. After I saw him the second time, all I wanted to do was get down on the ground as soon as possible, which I suppose was his intention all along. It is my understanding that the tfr was not communicated until XZ30 on the morning of my flight, just 1.5 hours before I left for my airport and 3 hours before the first leg of my trip. The local FBO and the 'hangar flyers' in the restaurant did not seem to know anything about the tfr either. In my experience, when there has been tfr's in the past, everyone in the FBO is mentioning it to each other, just to make sure everyone knows about it.

Original NASA ASRS Text

Title: AA5 ON PLEASURE FLT ENTERS TFR IN DFW AREA.

Narrative: I'M ENCLOSING A DETAILED DESCRIPTION OF THE EVENTS. MY PLANE BUSTED A TFR THAT WAS ONLY ANNOUNCED 2-3 HRS BEFORE I TOOK OFF. AN F-16 INTERCEPTED ME WHILE I WAS RETURNING TO MY HOME ARPT. I OBTAINED A DUATS BRIEFING, BUT DID NOT NOTICE THE TFR AS IT WAS APPARENTLY SANDWICHED BTWN THE USUAL CRAWFORD AND A NEW ONE NEAR HOU. THE HOU TFR WAS LISTED FIRST. HAD THE TFR BEEN LISTED FIRST OR WITH THE NORMAL ARPT NOTAMS, I WOULD HAVE SEEN IT. ALSO, THE PERSONNEL AT THE LCL FBO DID NOT SEEM TO KNOW ABOUT IT WHEN I LANDED THERE AND GOT GAS, JUST MINS BEFORE THE INTERCEPT. THE CHAIN OF EVENTS: I HAD LOST MY CELL PHONE 2 DAYS BEFORE AND MY FELLOW FLYING FRIENDS HAD TRIED TO CONTACT ME TO TELL ME ABOUT THE 'LAST MIN TFR' ONLY 30 MINS BEFORE I TOOK OFF. ALSO, I HAD BEEN WORKING A LOT THAT WK AND HAD NOT WATCHED THE NEWS. THE BIGGEST FACTOR THOUGH WAS THE 'HARD TO READ' AND 'POOR LOCATION' OF THE TFR IN THE DUATS SYS. FROM NOW ON, I WILL 'CALL' FOR A FLT BRIEFING. IN HINDSIGHT, ONE THING WAS VERY SURPRISING THAT YOU MIGHT WANT TO KNOW FOR THE FUTURE. IT'S THE FACT THE PLT OF THE F-16 NEVER DIRECTLY OR INDIRECTLY ADDRESSED ME IN ANY OF HIS COMS. HE NEVER SAID 'PLANE NEAR THE LAKE' OR MY TYPE PLANE, OR MY CALL SIGN, EVEN THOUGH I WAS USING THEM IN EACH AND EVERY CALL I MADE TO HIM. HIS LACK OF COM MADE IT VERY CONFUSING FOR ME TO KNOW WHAT HE WANTED ME TO DO. AFTER I SAW HIM THE SECOND TIME, ALL I WANTED TO DO WAS GET DOWN ON THE GND ASAP, WHICH I SUPPOSE WAS HIS INTENTION ALL ALONG. IT IS MY UNDERSTANDING THAT THE TFR WAS NOT COMMUNICATED UNTIL XZ30 ON THE MORNING OF MY FLT, JUST 1.5 HRS BEFORE I LEFT FOR MY ARPT AND 3 HRS BEFORE THE FIRST LEG OF MY TRIP. THE LCL FBO AND THE 'HANGAR FLYERS' IN THE RESTAURANT DID NOT SEEM TO KNOW ANYTHING ABOUT THE TFR EITHER. IN MY EXPERIENCE, WHEN THERE HAS BEEN TFR'S IN THE PAST, EVERYONE IN THE FBO IS MENTIONING IT TO EACH OTHER, JUST TO MAKE SURE EVERYONE KNOWS ABOUT IT.

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.