Information is recorded erroneously during an in-flight briefing of restr airspace. Using the inform...

Attributes
ACN	588615
Time
Date	200307
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : tth.vortac
State Reference	IN
Altitude	agl single value : 1500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : huf.tracon
Operator	general aviation : personal
Make Model Name	Bell 47
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Route In Use	enroute other
Flight Plan	None
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument pilot : cfi
Experience	flight time last 90 days : 50 flight time total : 3600 flight time type : 550
ASRS Report	588615
Person 2
Affiliation	government : faa
Function	other personnel
Events
Anomaly	airspace violation : entry non adherence : published procedure
Independent Detector	other controllerb
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

I flew through a tfr established over the town of montezuma, in, where the tfr was, and still is, a 5 NM and 5600 ft MSL restr. This flight originated in khef, and I was on the third leg of the trip on the way to the next fuel stop. The purpose of the flight was to ferry the aircraft to identification for a part 133 sling load contract. WX was excellent and I hoped to make it to north platte, nb, for the evening. I received an in-flight briefing from dayton FSS after departing from my first fuel stop. The specialist gave me 5 separate areas to be cautious of for the flight. 1) R-4501, 2) crane tfr off of hoosier VOR, 3) an air show north of indianapolis, 4) one on the pine bluff VOR and one off of the terra haute VOR. I did not know I flew through the tfr over montezuma, in, until I was briefed by TRACON supervisor. Mitigating circumstances: I received the proper information on the tfr's from the dayton FSS, but I wrote it down incorrectly, which is partly to blame because I was flying, trying to write down the information at the same time. Also, I think the controller may have thought I was headed for springfield, mo, since he gave me the tfr on the arkansas pine bluff VOR. Regardless though, I confused the hoosier radial/DME with the terra haute radial/DME. I wrote down that the tfr for the terra haute VOR was on the 223 degree radial, when it was actually on the 335 degree radial. It was actually the hoosier VOR that was using the 223 degree radial. Since I thought the tfr was southwest of terra haute, and I was flying north of terra haute, I didn't need to worry about the tfr. Contributing factors: 1) pilot in a hurry to fly as far west as possible. 2) should have gotten briefing on the ground, not in the air. 3) WX was very good, so I didn't bother with a full briefing, and only asked for tfr information. 4) this tfr has been in existence for a 1 1/2 yrs, why can't it be made into a restr area and put on the chart?

Original NASA ASRS Text

Title: INFO IS RECORDED ERRONEOUSLY DURING AN INFLT BRIEFING OF RESTR AIRSPACE. USING THE INFO RESULTS IN A FLT THROUGH AN ESTABLISHED BUT UNCHARTED RESTR AREA.

Narrative: I FLEW THROUGH A TFR ESTABLISHED OVER THE TOWN OF MONTEZUMA, IN, WHERE THE TFR WAS, AND STILL IS, A 5 NM AND 5600 FT MSL RESTR. THIS FLT ORIGINATED IN KHEF, AND I WAS ON THE THIRD LEG OF THE TRIP ON THE WAY TO THE NEXT FUEL STOP. THE PURPOSE OF THE FLT WAS TO FERRY THE ACFT TO ID FOR A PART 133 SLING LOAD CONTRACT. WX WAS EXCELLENT AND I HOPED TO MAKE IT TO NORTH PLATTE, NB, FOR THE EVENING. I RECEIVED AN INFLT BRIEFING FROM DAYTON FSS AFTER DEPARTING FROM MY FIRST FUEL STOP. THE SPECIALIST GAVE ME 5 SEPARATE AREAS TO BE CAUTIOUS OF FOR THE FLT. 1) R-4501, 2) CRANE TFR OFF OF HOOSIER VOR, 3) AN AIR SHOW N OF INDIANAPOLIS, 4) ONE ON THE PINE BLUFF VOR AND ONE OFF OF THE TERRA HAUTE VOR. I DID NOT KNOW I FLEW THROUGH THE TFR OVER MONTEZUMA, IN, UNTIL I WAS BRIEFED BY TRACON SUPVR. MITIGATING CIRCUMSTANCES: I RECEIVED THE PROPER INFO ON THE TFR'S FROM THE DAYTON FSS, BUT I WROTE IT DOWN INCORRECTLY, WHICH IS PARTLY TO BLAME BECAUSE I WAS FLYING, TRYING TO WRITE DOWN THE INFO AT THE SAME TIME. ALSO, I THINK THE CTLR MAY HAVE THOUGHT I WAS HEADED FOR SPRINGFIELD, MO, SINCE HE GAVE ME THE TFR ON THE ARKANSAS PINE BLUFF VOR. REGARDLESS THOUGH, I CONFUSED THE HOOSIER RADIAL/DME WITH THE TERRA HAUTE RADIAL/DME. I WROTE DOWN THAT THE TFR FOR THE TERRA HAUTE VOR WAS ON THE 223 DEG RADIAL, WHEN IT WAS ACTUALLY ON THE 335 DEG RADIAL. IT WAS ACTUALLY THE HOOSIER VOR THAT WAS USING THE 223 DEG RADIAL. SINCE I THOUGHT THE TFR WAS SW OF TERRA HAUTE, AND I WAS FLYING N OF TERRA HAUTE, I DIDN'T NEED TO WORRY ABOUT THE TFR. CONTRIBUTING FACTORS: 1) PLT IN A HURRY TO FLY AS FAR W AS POSSIBLE. 2) SHOULD HAVE GOTTEN BRIEFING ON THE GND, NOT IN THE AIR. 3) WX WAS VERY GOOD, SO I DIDN'T BOTHER WITH A FULL BRIEFING, AND ONLY ASKED FOR TFR INFO. 4) THIS TFR HAS BEEN IN EXISTENCE FOR A 1 1/2 YRS, WHY CAN'T IT BE MADE INTO A RESTR AREA AND PUT ON THE CHART?

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.

Information is recorded erroneously during an in-flight briefing of restr airspace. Using the information results in a flight through an established but uncharted restr area.