37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 338370 |
Time | |
Date | 199606 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : mci |
State Reference | MO |
Altitude | msl bound lower : 3000 msl bound upper : 3000 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | tower : mci tower : eug |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 135 |
Flight Phase | other |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | other : unknown |
Flight Phase | descent : approach |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 250 flight time total : 18000 flight time type : 4000 |
ASRS Report | 338370 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | conflict : airborne less severe non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other other |
Consequence | Other |
Miss Distance | horizontal : 12000 vertical : 500 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Situations | |
ATC Facility | procedure or policy : unspecified |
Narrative:
We were on downwind for runway 27 with several airplanes lined up on final. Approach was pointing out traffic for us to follow. We thought we had the aircraft to follow in sight at 1 O'clock as advised by approach control and we followed it, turning base to space ourselves correctly. This was the wrong aircraft, our aircraft to follow was actually at 11 O'clock. Once we were on base leg the other aircraft elected, or was told, to pull out of the pattern. He was talking to a different controller. This happens all the time, especially with parallel runways. Situation was made worse by the 2 aircraft involved being on different frequencys talking to different controllers. It seems to work out much better if the controller would state 'your traffic to follow is on a 5 mi final' rather than using clock position. We had TCASII, the cheap version. It does not seem to help much close to the airport. We did not get a TA.
Original NASA ASRS Text
Title: ACR SMT PIC CUTS ANOTHER ACFT OUT OF THE TFC PATTERN. TA GIVEN FOR ACFT TO FOLLOW BUT WRONG TFC SIGHTED. OTHER CTLR SENDS ACFT Y AROUND.
Narrative: WE WERE ON DOWNWIND FOR RWY 27 WITH SEVERAL AIRPLANES LINED UP ON FINAL. APCH WAS POINTING OUT TFC FOR US TO FOLLOW. WE THOUGHT WE HAD THE ACFT TO FOLLOW IN SIGHT AT 1 O'CLOCK AS ADVISED BY APCH CTL AND WE FOLLOWED IT, TURNING BASE TO SPACE OURSELVES CORRECTLY. THIS WAS THE WRONG ACFT, OUR ACFT TO FOLLOW WAS ACTUALLY AT 11 O'CLOCK. ONCE WE WERE ON BASE LEG THE OTHER ACFT ELECTED, OR WAS TOLD, TO PULL OUT OF THE PATTERN. HE WAS TALKING TO A DIFFERENT CTLR. THIS HAPPENS ALL THE TIME, ESPECIALLY WITH PARALLEL RWYS. SIT WAS MADE WORSE BY THE 2 ACFT INVOLVED BEING ON DIFFERENT FREQS TALKING TO DIFFERENT CTLRS. IT SEEMS TO WORK OUT MUCH BETTER IF THE CTLR WOULD STATE 'YOUR TFC TO FOLLOW IS ON A 5 MI FINAL' RATHER THAN USING CLOCK POS. WE HAD TCASII, THE CHEAP VERSION. IT DOES NOT SEEM TO HELP MUCH CLOSE TO THE ARPT. WE DID NOT GET A TA.
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.