Tfr illegally entered by an errant BE50 flight proceeding southwest, 25 NM southeast of gnv.

Attributes
ACN	636167
Time
Date	200410
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : gnv.vortac
State Reference	FL
Altitude	msl single value : 2500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : jax.tracon
Operator	general aviation : personal
Make Model Name	Twin Bonanza 50
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Flight Plan	None
Aircraft 2
Controlling Facilities	tracon : jax.tracon
Operator	other
Make Model Name	Fighting Falcon F16
Operating Under FAR Part	Part 91
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : atp
ASRS Report	636167
Person 2
Affiliation	other
Function	observation : passenger
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 35 flight time total : 5000 flight time type : 100
ASRS Report	635827
Events
Anomaly	airspace violation : entry inflight encounter other non adherence : far non adherence : published procedure
Independent Detector	other controllera other other : 3
Resolutory Action	none taken : detected after the fact other
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airspace Structure Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While en route from kay larkin airport (28J) as PF, we observed an F16 aircraft overhead our position. While monitoring guard (121.5) the pilot of the F16 idented us by our approximately position reference the gnv VOR. My son, who was handling the communications, relayed our identify and type aircraft to the F16 pilot. We were then cleared via the F16 pilot to resume our own navigation to our destination southeast of ocf VOR. We requested a phone number from jax approach to follow up on the incident after landing. Upon contacting jax approach via telephone, my son was advised that we had encroached on a tfr centered on the gnv VOR. We were aware of tfr's in the orlando, tampa, and miami area but were not aware of the one over gainesville. That morning we had observed the web site and did not remember any tfr that would conflict with our route of flight, however, we had not initially planned on traveling as far north as 28J.

Original NASA ASRS Text

Title: TFR ILLEGALLY ENTERED BY AN ERRANT BE50 FLT PROCEEDING SW, 25 NM SE OF GNV.

Narrative: WHILE ENRTE FROM KAY LARKIN ARPT (28J) AS PF, WE OBSERVED AN F16 ACFT OVERHEAD OUR POS. WHILE MONITORING GUARD (121.5) THE PLT OF THE F16 IDENTED US BY OUR APPROX POS REF THE GNV VOR. MY SON, WHO WAS HANDLING THE COMS, RELAYED OUR IDENT AND TYPE ACFT TO THE F16 PLT. WE WERE THEN CLRED VIA THE F16 PLT TO RESUME OUR OWN NAV TO OUR DEST SE OF OCF VOR. WE REQUESTED A PHONE NUMBER FROM JAX APCH TO FOLLOW UP ON THE INCIDENT AFTER LNDG. UPON CONTACTING JAX APCH VIA TELEPHONE, MY SON WAS ADVISED THAT WE HAD ENCROACHED ON A TFR CTRED ON THE GNV VOR. WE WERE AWARE OF TFR'S IN THE ORLANDO, TAMPA, AND MIAMI AREA BUT WERE NOT AWARE OF THE ONE OVER GAINESVILLE. THAT MORNING WE HAD OBSERVED THE WEB SITE AND DID NOT REMEMBER ANY TFR THAT WOULD CONFLICT WITH OUR RTE OF FLT, HOWEVER, WE HAD NOT INITIALLY PLANNED ON TRAVELING AS FAR N AS 28J.

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.