37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 451431 |
Time | |
Date | 199910 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sfq.airport |
State Reference | VA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | M-20 J (201) |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | landing : roll |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : multi engine pilot : commercial |
Experience | flight time last 90 days : 30 flight time total : 1500 flight time type : 400 |
ASRS Report | 451431 |
Events | |
Anomaly | non adherence : far non adherence : published procedure other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Sfq, my home airport, has 3 runways. For 10-12 weeks, the ATIS has reported 1) NDB decommissioned, 2) runway 15/33 closed, 3) runway 4/22 localizer out. On the date of the occurrence, runway 7/25 was added as also closed. I failed to note this and landed on runway 25, which the wind favored. I had become so accustomed to the same 3 ATIS messages that I only noted wind data. It was a lesson in inattentiveness. Callback conversation with reporter revealed the following information: the pilot reports that the ATIS contained lengthy airport equipment OTS and runway closures for an upcoming event. This had been this way for several days and resulted in the pilot listening only for the winds and altimeter setting. The closure of the runway failed to catch his attention. The closure was for operations near the runway and not because the surface was unusable. Runway closed marking only caught the pilot's attention after he was committed to the landing.
Original NASA ASRS Text
Title: A MOONEY PLT LANDED ON A CLOSED RWY AT SFQ.
Narrative: SFQ, MY HOME ARPT, HAS 3 RWYS. FOR 10-12 WKS, THE ATIS HAS RPTED 1) NDB DECOMMISSIONED, 2) RWY 15/33 CLOSED, 3) RWY 4/22 LOC OUT. ON THE DATE OF THE OCCURRENCE, RWY 7/25 WAS ADDED AS ALSO CLOSED. I FAILED TO NOTE THIS AND LANDED ON RWY 25, WHICH THE WIND FAVORED. I HAD BECOME SO ACCUSTOMED TO THE SAME 3 ATIS MESSAGES THAT I ONLY NOTED WIND DATA. IT WAS A LESSON IN INATTENTIVENESS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE PLT RPTS THAT THE ATIS CONTAINED LENGTHY ARPT EQUIP OTS AND RWY CLOSURES FOR AN UPCOMING EVENT. THIS HAD BEEN THIS WAY FOR SEVERAL DAYS AND RESULTED IN THE PLT LISTENING ONLY FOR THE WINDS AND ALTIMETER SETTING. THE CLOSURE OF THE RWY FAILED TO CATCH HIS ATTN. THE CLOSURE WAS FOR OPS NEAR THE RWY AND NOT BECAUSE THE SURFACE WAS UNUSABLE. RWY CLOSED MARKING ONLY CAUGHT THE PLT'S ATTN AFTER HE WAS COMMITTED TO THE LNDG.
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.