37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 141281 |
Time | |
Date | 199004 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : ord |
State Reference | IL |
Altitude | msl bound lower : 3000 msl bound upper : 3400 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : ord tower : ord artcc : zdc |
Operator | common carrier : air carrier |
Make Model Name | Medium Transport, High Wing, 2 Turboprop Eng |
Navigation In Use | Other Other |
Flight Phase | cruise other cruise other descent : approach |
Route In Use | approach : visual arrival other enroute : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Large Transport, Low Wing, 3 Turbojet Eng |
Flight Phase | cruise other cruise other descent : approach |
Route In Use | arrival other enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : cfi pilot : commercial |
Experience | flight time last 90 days : 210 flight time total : 2300 flight time type : 1300 |
ASRS Report | 141281 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : nmac incursion : runway non adherence : required legal separation other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | other |
Consequence | Other |
Miss Distance | horizontal : 0 vertical : 350 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Beware visual apches in ord! We had turned on and were established on 27L at ord. About 2 mi outside the marker I noticed other aircraft (3 engine heavy jet) overshooting 27R (or possibly joining 27L). He was about 300-400' below us. We asked tower what he was doing. They replied 'he is now correcting back to the right side.' fortunately we had been given a high turn on and were still correcting for a full scale fly down on the glide slope. Had we been on the glide slope I don't think we would have missed each other. Based on the angle of bank the other aircraft was using, I feel he was joining 27L. Only after the other aircraft was under us did he increase his angle of bank. I think the way to prevent this from happening again in the future is to always give out the localizer frequency any time simultaneous or parallel apches are in use (even visuals). I.e., XXXX 123 heavy runway 27R visual approach localizer frequency 110.5.
Original NASA ASRS Text
Title: AN LGT INTRUDES ON THE ILS 27L APCH COURSE THAT IS OCCUPIED BY ACFT X. ACFT Y OVERSHOT HIS TURN ONTO RWY 27R.
Narrative: BEWARE VISUAL APCHES IN ORD! WE HAD TURNED ON AND WERE ESTABLISHED ON 27L AT ORD. ABOUT 2 MI OUTSIDE THE MARKER I NOTICED OTHER ACFT (3 ENGINE HEAVY JET) OVERSHOOTING 27R (OR POSSIBLY JOINING 27L). HE WAS ABOUT 300-400' BELOW US. WE ASKED TWR WHAT HE WAS DOING. THEY REPLIED 'HE IS NOW CORRECTING BACK TO THE RIGHT SIDE.' FORTUNATELY WE HAD BEEN GIVEN A HIGH TURN ON AND WERE STILL CORRECTING FOR A FULL SCALE FLY DOWN ON THE GLIDE SLOPE. HAD WE BEEN ON THE GLIDE SLOPE I DON'T THINK WE WOULD HAVE MISSED EACH OTHER. BASED ON THE ANGLE OF BANK THE OTHER ACFT WAS USING, I FEEL HE WAS JOINING 27L. ONLY AFTER THE OTHER ACFT WAS UNDER US DID HE INCREASE HIS ANGLE OF BANK. I THINK THE WAY TO PREVENT THIS FROM HAPPENING AGAIN IN THE FUTURE IS TO ALWAYS GIVE OUT THE LOC FREQ ANY TIME SIMULTANEOUS OR PARALLEL APCHES ARE IN USE (EVEN VISUALS). I.E., XXXX 123 HEAVY RWY 27R VISUAL APCH LOC FREQ 110.5.
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.