37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 720975 |
Time | |
Date | 200612 |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | airport : dtw.airport |
State Reference | MI |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air taxi |
Make Model Name | PA-60 600 Aerostar |
Operating Under FAR Part | Part 135 |
Flight Phase | landing : roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : single pilot |
Qualification | pilot : atp pilot : multi engine |
Experience | flight time last 90 days : 103 flight time total : 6232 flight time type : 4650 |
ASRS Report | 720975 |
Events | |
Anomaly | ground encounters other incursion : runway incursion : landing without clearance |
Independent Detector | other flight crewb |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airport |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
En route to dtw from phl; I was cleared for the visual approach to runway 22R. Knowing that all runways except runway 22R were notamed closed and seeing the darkened runways on the south side of the terminal I made my approach and landed on the first lighted runway on the north side of the terminal area. Unfortunately; this happened to be runway 22L; which was closed and for which I was not cleared either for a visual approach or for landing. Due to the visibility and the fact that runway 22L had captured my attention; I never saw the correct runway; which was located several mi to my right front. In fact runway 22L was the only runway I did see on my approach to the airport. What really caused the problem was my lack of situational awareness; inadequate review of the airport diagram (which I had looked at and was lying open beside me); and a decision on my part not to follow the localizer and GS to the proper runway even though I was on a visual approach. These factors were complicated by the fact that even though the runway was closed it was lighted and my approach was rushed because I didn't descend from my cruise altitude of 8000 ft MSL until I was close to the airport.
Original NASA ASRS Text
Title: COMPLACENCY RESULTS IN PA60 LNDG ON WRONG; CLOSED RWY AT DTW.
Narrative: ENRTE TO DTW FROM PHL; I WAS CLRED FOR THE VISUAL APCH TO RWY 22R. KNOWING THAT ALL RWYS EXCEPT RWY 22R WERE NOTAMED CLOSED AND SEEING THE DARKENED RWYS ON THE S SIDE OF THE TERMINAL I MADE MY APCH AND LANDED ON THE FIRST LIGHTED RWY ON THE N SIDE OF THE TERMINAL AREA. UNFORTUNATELY; THIS HAPPENED TO BE RWY 22L; WHICH WAS CLOSED AND FOR WHICH I WAS NOT CLRED EITHER FOR A VISUAL APCH OR FOR LNDG. DUE TO THE VISIBILITY AND THE FACT THAT RWY 22L HAD CAPTURED MY ATTN; I NEVER SAW THE CORRECT RWY; WHICH WAS LOCATED SEVERAL MI TO MY R FRONT. IN FACT RWY 22L WAS THE ONLY RWY I DID SEE ON MY APCH TO THE ARPT. WHAT REALLY CAUSED THE PROB WAS MY LACK OF SITUATIONAL AWARENESS; INADEQUATE REVIEW OF THE ARPT DIAGRAM (WHICH I HAD LOOKED AT AND WAS LYING OPEN BESIDE ME); AND A DECISION ON MY PART NOT TO FOLLOW THE LOC AND GS TO THE PROPER RWY EVEN THOUGH I WAS ON A VISUAL APCH. THESE FACTORS WERE COMPLICATED BY THE FACT THAT EVEN THOUGH THE RWY WAS CLOSED IT WAS LIGHTED AND MY APCH WAS RUSHED BECAUSE I DIDN'T DSND FROM MY CRUISE ALT OF 8000 FT MSL UNTIL I WAS CLOSE TO THE ARPT.
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.