A husky A-1 pilot flies into the eastern edge of a tfr that was established 5 NM west of 1v5 airport...

Attributes
ACN	554238
Time
Date	200207
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : 1v5.airport
State Reference	CO
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Christen A-1 Huskey
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Flight Plan	None
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : cfi pilot : commercial pilot : multi engine
Experience	flight time last 90 days : 50 flight time total : 2900 flight time type : 1500
ASRS Report	554238
Person 2
Function	oversight : airport manager
Events
Anomaly	airspace violation : entry non adherence : far other anomaly other anomaly other other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated faa : reviewed incident with flight crew Other
Supplementary
Problem Areas	Environmental Factor FAA Chart Or Publication Airspace Structure Flight Crew Human Performance
Primary Problem	FAA
Air Traffic Incident	Inter Facility Coordination Failure

Narrative:

Upon announcing my intent to enter the traffic pattern and land at boulder airport (1v5), I heard an announcement on CTAF that there was a tfr in effect due to a fire 5 mi west of boulder, for 3 mi and 3000 ft, and that boulder airport was closed. I immediately diverted to longmont airport (2v2), where I contacted denver FSS. The briefer told me that he had no NOTAMS or restrs for bolder airport. He confirmed this with his supervisor. I then called the FBO at boulder that operates unicom and received a recorded message to leave a message. I called the other FBO at boulder, and was told that the denver FSS had just called them asking about the airport being closed. Neither the FBO nor FSS knew anything about the airport being closed. Furthermore, I was also told that aircraft were taking off and landing as we spoke. While I was having this conversation, another pilot, who had also diverted to longmont, called denver FSS and was also told that there were no NOTAMS or restrs for boulder airport. At this time we both decided to return to boulder airport. I flew a close-in pattern at boulder in order to remain well clear of the fire area. After landing and taxiing off of the runway, I heard the following on CTAF: 'there is a tfr in place at boulder airport. All traffic is to land from the east and take off to the east.' as I was putting my plane in the hangar, I noticed the airport manager entering his office, so I went there to find out what he knew. He showed me a document that he aid the FAA had earlier that day. It indicated that because of the activity at the fire scene, all traffic at boulder airport was to land from the east and depart to the east. I had landed on the normally preferred runway 8. According to the document the airport manager showed me, I believe that I should have flown a straight-in landing to runway 26. The restr as presented to me by the airport manager certainly makes sense and would be easy enough to follow. Perhaps if I had been able to contact the FBO that handles bolder unicom, I would not have made the mistake, but 2 attempts at doing so resulted in a recorded message to leave a message.

Original NASA ASRS Text

Title: A HUSKY A-1 PLT FLIES INTO THE EASTERN EDGE OF A TFR THAT WAS ESTABLISHED 5 NM W OF 1V5 ARPT WHEN MAKING THE APCH TO RWY 8 AT 1V5, CO.

Narrative: UPON ANNOUNCING MY INTENT TO ENTER THE TFC PATTERN AND LAND AT BOULDER ARPT (1V5), I HEARD AN ANNOUNCEMENT ON CTAF THAT THERE WAS A TFR IN EFFECT DUE TO A FIRE 5 MI W OF BOULDER, FOR 3 MI AND 3000 FT, AND THAT BOULDER ARPT WAS CLOSED. I IMMEDIATELY DIVERTED TO LONGMONT ARPT (2V2), WHERE I CONTACTED DENVER FSS. THE BRIEFER TOLD ME THAT HE HAD NO NOTAMS OR RESTRS FOR BOLDER ARPT. HE CONFIRMED THIS WITH HIS SUPVR. I THEN CALLED THE FBO AT BOULDER THAT OPERATES UNICOM AND RECEIVED A RECORDED MESSAGE TO LEAVE A MESSAGE. I CALLED THE OTHER FBO AT BOULDER, AND WAS TOLD THAT THE DENVER FSS HAD JUST CALLED THEM ASKING ABOUT THE ARPT BEING CLOSED. NEITHER THE FBO NOR FSS KNEW ANYTHING ABOUT THE ARPT BEING CLOSED. FURTHERMORE, I WAS ALSO TOLD THAT ACFT WERE TAKING OFF AND LNDG AS WE SPOKE. WHILE I WAS HAVING THIS CONVERSATION, ANOTHER PLT, WHO HAD ALSO DIVERTED TO LONGMONT, CALLED DENVER FSS AND WAS ALSO TOLD THAT THERE WERE NO NOTAMS OR RESTRS FOR BOULDER ARPT. AT THIS TIME WE BOTH DECIDED TO RETURN TO BOULDER ARPT. I FLEW A CLOSE-IN PATTERN AT BOULDER IN ORDER TO REMAIN WELL CLR OF THE FIRE AREA. AFTER LNDG AND TAXIING OFF OF THE RWY, I HEARD THE FOLLOWING ON CTAF: 'THERE IS A TFR IN PLACE AT BOULDER ARPT. ALL TFC IS TO LAND FROM THE E AND TAKE OFF TO THE E.' AS I WAS PUTTING MY PLANE IN THE HANGAR, I NOTICED THE ARPT MGR ENTERING HIS OFFICE, SO I WENT THERE TO FIND OUT WHAT HE KNEW. HE SHOWED ME A DOCUMENT THAT HE AID THE FAA HAD EARLIER THAT DAY. IT INDICATED THAT BECAUSE OF THE ACTIVITY AT THE FIRE SCENE, ALL TFC AT BOULDER ARPT WAS TO LAND FROM THE E AND DEPART TO THE E. I HAD LANDED ON THE NORMALLY PREFERRED RWY 8. ACCORDING TO THE DOCUMENT THE ARPT MGR SHOWED ME, I BELIEVE THAT I SHOULD HAVE FLOWN A STRAIGHT-IN LNDG TO RWY 26. THE RESTR AS PRESENTED TO ME BY THE ARPT MGR CERTAINLY MAKES SENSE AND WOULD BE EASY ENOUGH TO FOLLOW. PERHAPS IF I HAD BEEN ABLE TO CONTACT THE FBO THAT HANDLES BOLDER UNICOM, I WOULD NOT HAVE MADE THE MISTAKE, BUT 2 ATTEMPTS AT DOING SO RESULTED IN A RECORDED MESSAGE TO LEAVE A MESSAGE.

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.

A husky A-1 pilot flies into the eastern edge of a tfr that was established 5 NM west of 1v5 airport when making the approach to runway 8 at 1v5, co.