37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 349490 |
Time | |
Date | 199610 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : pit |
State Reference | PA |
Altitude | msl bound lower : 3000 msl bound upper : 3000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : pit |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 135 |
Flight Phase | descent : approach landing other |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 50 flight time total : 5000 flight time type : 2000 |
ASRS Report | 349490 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued new clearance |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
This is a classic example of being complacent during VMC approach and landing. During night VMC, approach asked if we could see a C130 descending for runway 32. After locating and calling traffic in sight approach then told us to follow the traffic to runway 32. After looking inside to confirm airspds to begin configuring, I looked back outside and had lost the traffic in ground lighting, but saw what I assumed to be runway 32. While continuing to slow and configure, the first officer commented that we appeared to be lining up for runway 28L. At the same time, approach told us that we appeared to be lining up for runway 28L. I configured this and prepared to go around, but was cleared for approach and landing to runway 28L and continued to an uneventful landing with no traffic conflicts. Although no other aircraft were involved, I was very embarrassed and have taken from this incident the realization that perfect VMC is the most likely time to be paying the least attention. Under different circumstances, the consequences could be severe.
Original NASA ASRS Text
Title: TURBOJET CARGO CARRIER LINES UP ON THE WRONG RWY AT PIT.
Narrative: THIS IS A CLASSIC EXAMPLE OF BEING COMPLACENT DURING VMC APCH AND LNDG. DURING NIGHT VMC, APCH ASKED IF WE COULD SEE A C130 DSNDING FOR RWY 32. AFTER LOCATING AND CALLING TFC IN SIGHT APCH THEN TOLD US TO FOLLOW THE TFC TO RWY 32. AFTER LOOKING INSIDE TO CONFIRM AIRSPDS TO BEGIN CONFIGURING, I LOOKED BACK OUTSIDE AND HAD LOST THE TFC IN GND LIGHTING, BUT SAW WHAT I ASSUMED TO BE RWY 32. WHILE CONTINUING TO SLOW AND CONFIGURE, THE FO COMMENTED THAT WE APPEARED TO BE LINING UP FOR RWY 28L. AT THE SAME TIME, APCH TOLD US THAT WE APPEARED TO BE LINING UP FOR RWY 28L. I CONFIGURED THIS AND PREPARED TO GAR, BUT WAS CLRED FOR APCH AND LNDG TO RWY 28L AND CONTINUED TO AN UNEVENTFUL LNDG WITH NO TFC CONFLICTS. ALTHOUGH NO OTHER ACFT WERE INVOLVED, I WAS VERY EMBARRASSED AND HAVE TAKEN FROM THIS INCIDENT THE REALIZATION THAT PERFECT VMC IS THE MOST LIKELY TIME TO BE PAYING THE LEAST ATTN. UNDER DIFFERENT CIRCUMSTANCES, THE CONSEQUENCES COULD BE SEVERE.
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.