37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 744349 |
Time | |
Date | 200707 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : dnl.airport |
State Reference | GA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | M-20 Series Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : takeoff roll ground : maintenance |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Experience | flight time last 90 days : 20 flight time total : 1620 flight time type : 1145 |
ASRS Report | 744349 |
Events | |
Anomaly | incursion : runway non adherence : far |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Airport Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Aircraft arrived at dnl airport with knowledge that runway 5 was closed. When departing aircraft requested a runway 5 departure in error that was confirmed by augusta tower. Aircraft taxied in communication with dnl unicom to runway 5 and was cleared for departure. After departing it was observed that runway 5 was still closed. Pilot was in error for not verifying the status of the runway prior to departure. Lessons learned: to review all NOTAMS prior to takeoff. Unicom frequency communications were acknowledged by personnel on the ground at dnl; but no mention was made of runway 5 being closed. Augusta tower; the controling frequency for IFR traffic was aware of the runway closure yet authority/authorized the departure. So all 3 parties involved failed to review a known condition at the departure airport. Departure was executed normally with no risk to reporting aircraft; other aircraft or ground personnel. This might not be the case in other situations so clarity of communications concerning abnormal airport conditions need to be very precise.
Original NASA ASRS Text
Title: M20P PLT; UNICOM OPERATOR AND REMOTE TOWER CTLR AT AGS ALL FAIL TO FORESTALL TKOF FROM RWY 05 AT DNL; WHICH WAS CLOSED VIA NOTAM.
Narrative: ACFT ARRIVED AT DNL ARPT WITH KNOWLEDGE THAT RWY 5 WAS CLOSED. WHEN DEPARTING ACFT REQUESTED A RWY 5 DEP IN ERROR THAT WAS CONFIRMED BY AUGUSTA TWR. ACFT TAXIED IN COM WITH DNL UNICOM TO RWY 5 AND WAS CLRED FOR DEP. AFTER DEPARTING IT WAS OBSERVED THAT RWY 5 WAS STILL CLOSED. PLT WAS IN ERROR FOR NOT VERIFYING THE STATUS OF THE RWY PRIOR TO DEP. LESSONS LEARNED: TO REVIEW ALL NOTAMS PRIOR TO TKOF. UNICOM FREQ COMS WERE ACKNOWLEDGED BY PERSONNEL ON THE GND AT DNL; BUT NO MENTION WAS MADE OF RWY 5 BEING CLOSED. AUGUSTA TWR; THE CTLING FREQ FOR IFR TFC WAS AWARE OF THE RWY CLOSURE YET AUTH THE DEP. SO ALL 3 PARTIES INVOLVED FAILED TO REVIEW A KNOWN CONDITION AT THE DEP ARPT. DEP WAS EXECUTED NORMALLY WITH NO RISK TO RPTING ACFT; OTHER ACFT OR GND PERSONNEL. THIS MIGHT NOT BE THE CASE IN OTHER SITUATIONS SO CLARITY OF COMS CONCERNING ABNORMAL ARPT CONDITIONS NEED TO BE VERY PRECISE.
Data retrieved from NASA's ASRS site as of January 2009 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.