 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of a B737-300 overshot final course during a visual approach to a parallel runway and ended up flying through the final of another set of parallel runways. The first officer flying the aircraft was distraction by the setting sun in his eyes. Approach to wrong runway.
| Attributes | |
| ACN | 338511 |
| Time | |
| Date | 199606 |
| Day | Thu |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : lax |
| State Reference | CA |
| Altitude | msl bound lower : 3000 msl bound upper : 3000 |
| Environment | |
| Flight Conditions | Marginal |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | tracon : lax |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | descent : approach |
| Route In Use | approach : visual arrival other arrival star : star |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : flight engineer pilot : atp |
| Experience | flight time last 90 days : 240 flight time total : 12000 flight time type : 240 |
| ASRS Report | 338511 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | non adherence : clearance other anomaly other other anomaly other other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | flight crew : returned to intended course or assigned course other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
During approach we were slowed significantly and kept high while following much slower traffic. Subsequently, while issued a visual approach we had to dirty-up and configure, make altitude adjustments, clear for traffic, and run checklists. Upon turning base, the runway which I had previously called in sight for a visual was lost in smog and haze while looking into the sunset, and the runway that I thought was runway 24R was in fact runway 25R on the south complex. I did not realize this until on final and I had a chance to look at my instruments. At this time tower also said we had overshot final. Because we were high on approach we were no conflict to south complex traffic, however, approach control should be vigilant to help keep traffic to the north -- and be aware that sometimes what may be visual (VFR) from one sector might not be VFR from another!
Original NASA ASRS Text
Title: FLC OF A B737-300 OVERSHOT FINAL COURSE DURING A VISUAL APCH TO A PARALLEL RWY AND ENDED UP FLYING THROUGH THE FINAL OF ANOTHER SET OF PARALLEL RWYS. THE FO FLYING THE ACFT WAS DISTR BY THE SETTING SUN IN HIS EYES. APCH TO WRONG RWY.
Narrative: DURING APCH WE WERE SLOWED SIGNIFICANTLY AND KEPT HIGH WHILE FOLLOWING MUCH SLOWER TFC. SUBSEQUENTLY, WHILE ISSUED A VISUAL APCH WE HAD TO DIRTY-UP AND CONFIGURE, MAKE ALT ADJUSTMENTS, CLR FOR TFC, AND RUN CHKLISTS. UPON TURNING BASE, THE RWY WHICH I HAD PREVIOUSLY CALLED IN SIGHT FOR A VISUAL WAS LOST IN SMOG AND HAZE WHILE LOOKING INTO THE SUNSET, AND THE RWY THAT I THOUGHT WAS RWY 24R WAS IN FACT RWY 25R ON THE S COMPLEX. I DID NOT REALIZE THIS UNTIL ON FINAL AND I HAD A CHANCE TO LOOK AT MY INSTS. AT THIS TIME TWR ALSO SAID WE HAD OVERSHOT FINAL. BECAUSE WE WERE HIGH ON APCH WE WERE NO CONFLICT TO S COMPLEX TFC, HOWEVER, APCH CTL SHOULD BE VIGILANT TO HELP KEEP TFC TO THE N -- AND BE AWARE THAT SOMETIMES WHAT MAY BE VISUAL (VFR) FROM ONE SECTOR MIGHT NOT BE VFR FROM ANOTHER!
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.