37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1201815 |
Time | |
Date | 201408 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Flight Plan | VFR |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Private |
Experience | Flight Crew Last 90 Days 25 Flight Crew Total 900 Flight Crew Type 150 |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Narrative:
Flew in full daylight from ZZZ to ZZZ1 about 37 miles straight line on august Y 2014. From ZZZ weather conditions were scattered clouds at probably 10-12;000' MSL and unlimited visibility with winds less than 10 knots. Therefore; no weather briefing was sought from the FSS. For several days; the AWOS had been broadcasting a local NOTAM; or remarks; that airport was closed through august X; 2014. Before pattern entry AWOS was checked 10 miles out and same AWOS local NOTAM or remarks were broadcast; i.e. Airport closed through august X; 2014 along with current wind data etc. Operator called in his entry into the traffic pattern; his base leg; and final leg without any further advisory or any response as to airport status (open or closed) from the FBO 'manager' (a subcontractor or lessee from the city which owns the airport) present on the ground on a hand-held radio. On final; operator saw no 'X' markings on the runway to indicate airport was closed; and landed. Leaving the active runway on one of the exits to the main taxiway; operator saw some plastic barricades which were wide open in the center to allow aircraft to taxi to the main taxiway and the ramp. Operator concluded that closure makings were being removed and these barricades were pushed to the side to be collected but were open for passage; a conclusion consistent with the announced closure lasting through august X; 2014 and this date being a day later. Operator parked the plane and took one of the airport 'courtesy cars' into town and returned perhaps an hour or two later. Operator noticed a couple of planes shooting 'touch and go' landings. Operator prepared his aircraft to leave and checked the AWOS. The remarks/local NOTAM re closure through august X; 2014 had been removed. Operator taxied to a run-up area. On the way there; operator noticed that the barricades had been picked up which was consistent with the conclusion that earlier they had been set aside for later collection. No markings existed on the runway indicating any closure and other aircraft were already using the airport. Operator received a certified letter from the FAA. The letter stated that there would be an investigation of 'landing [airplane] at a closed airport; ZZZ1 on august Y 2014.' operator attempted to find any published NOTAM re ZZZ1 closure but the FSS said they 'were not kept more than 2 or 3 days.' however; operator obtained the allegedly published NOTAM via an on-line information request as an attachment to an email from the FAA investigator which states the closure period to be through august Y 2014. Operator has requested a copy of the AWOS recording remarks (repeated every time AWOS was accessed) from the city with no response thus far. It appears that a great deal of confusion came from the broadcast of a local NOTAM stating a different closure period through august Y; 2014; than the published NOTAM which was apparently rescinded some time during the early afternoon of august Y 2014. Removal of whatever temporary closure markings or devices was haphazard resulting in the lack of closure markings before whatever time it was that the published NOTAM was rescinded. No construction; surface repair was going on to alert anyone. The local FBO 'manager' remained silent when it was obvious; or should have been; that an aircraft was approaching the field to land; entering downwind; turning base and then final and broadcasting each step on unicom. There is no reason for such a conflict being created by an inconsistent local NOTAM broadcast on the AWOS frequency and haphazard removal of closure markings or devices. The two other aircraft besides mine that were operating at the airport on august Y; suggests that users may have been confused by the situation. It is unknown if the operators of these other aircraft were seen to be in violation of the published NOTAM and/or were reported to the FAA.
Original NASA ASRS Text
Title: Small aircraft pilot reports receiving a letter from the FAA indicating that he is being investigated for landing at a closed airport. A NOTAM was in existence that accurately reflected the closure but the AWOS only indicated the airport would be closed through the previous day. No X's were on the runway.
Narrative: Flew in full daylight from ZZZ to ZZZ1 about 37 miles straight line on August Y 2014. From ZZZ weather conditions were scattered clouds at probably 10-12;000' MSL and unlimited visibility with winds less than 10 knots. Therefore; no weather briefing was sought from the FSS. For several days; the AWOS had been broadcasting a local NOTAM; or remarks; that airport was closed through August X; 2014. Before pattern entry AWOS was checked 10 miles out and same AWOS local NOTAM or remarks were broadcast; i.e. airport closed through August X; 2014 along with current wind data etc. Operator called in his entry into the traffic pattern; his base leg; and final leg without any further advisory or any response as to airport status (open or closed) from the FBO 'Manager' (a subcontractor or lessee from the City which owns the airport) present on the ground on a hand-held radio. On final; Operator saw no 'X' markings on the runway to indicate airport was closed; and landed. Leaving the active runway on one of the exits to the main taxiway; operator saw some plastic barricades which were wide open in the center to allow aircraft to taxi to the main taxiway and the ramp. Operator concluded that closure makings were being removed and these barricades were pushed to the side to be collected but were open for passage; a conclusion consistent with the announced closure lasting through August X; 2014 and this date being a day later. Operator parked the plane and took one of the airport 'courtesy cars' into town and returned perhaps an hour or two later. Operator noticed a couple of planes shooting 'touch and go' landings. Operator prepared his aircraft to leave and checked the AWOS. The remarks/local NOTAM re closure through August X; 2014 had been removed. Operator taxied to a run-up area. On the way there; operator noticed that the barricades had been picked up which was consistent with the conclusion that earlier they had been set aside for later collection. No markings existed on the runway indicating any closure and other aircraft were already using the airport. Operator received a certified letter from the FAA. The letter stated that there would be an investigation of 'landing [airplane] at a closed airport; ZZZ1 on August Y 2014.' Operator attempted to find any published NOTAM re ZZZ1 closure but the FSS said they 'were not kept more than 2 or 3 days.' However; Operator obtained the allegedly published NOTAM via an on-line information request as an attachment to an email from the FAA investigator which states the closure period to be through August Y 2014. Operator has requested a copy of the AWOS recording remarks (repeated every time AWOS was accessed) from the City with no response thus far. It appears that a great deal of confusion came from the broadcast of a local NOTAM stating a different closure period through August Y; 2014; than the published NOTAM which was apparently rescinded some time during the early afternoon of August Y 2014. Removal of whatever temporary closure markings or devices was haphazard resulting in the lack of closure markings before whatever time it was that the published NOTAM was rescinded. No construction; surface repair was going on to alert anyone. The local FBO 'manager' remained silent when it was obvious; or should have been; that an aircraft was approaching the field to land; entering downwind; turning base and then final and broadcasting each step on UNICOM. There is no reason for such a conflict being created by an inconsistent local NOTAM broadcast on the AWOS frequency and haphazard removal of closure markings or devices. The two other aircraft besides mine that were operating at the airport on August Y; suggests that users may have been confused by the situation. It is unknown if the operators of these other aircraft were seen to be in violation of the published NOTAM and/or were reported to the FAA.
Data retrieved from NASA's ASRS site 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.