37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 445435 |
Time | |
Date | 199908 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : mci.airport |
State Reference | MO |
Altitude | msl bound lower : 5200 msl bound upper : 7000 |
Environment | |
Flight Conditions | VMC |
Weather Elements | Turbulence |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : mci.tracon |
Operator | common carrier : air carrier |
Make Model Name | B727-200 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 19l Other |
Flight Phase | descent : approach |
Route In Use | approach : instrument precision arrival : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : mci.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain |
Qualification | pilot : flight engineer pilot : cfi pilot : atp pilot : multi engine |
Experience | flight time last 90 days : 220 flight time total : 15000 flight time type : 10200 |
ASRS Report | 445435 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : atp pilot : commercial pilot : flight engineer pilot : instrument |
Experience | flight time last 90 days : 210 flight time total : 8500 flight time type : 3600 |
ASRS Report | 445600 |
Events | |
Anomaly | conflict : airborne critical non adherence : required legal separation non adherence : published procedure other anomaly other |
Independent Detector | aircraft equipment : tcas other flight crewa other flight crewb other other : 3 |
Resolutory Action | controller : issued new clearance flight crew : took evasive action |
Miss Distance | horizontal : 10000 vertical : 0 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
Aircraft on 150 degree heading, mci approach control being vectored for visual approach to runway 19L mci. Airspeed 250 KIAS altitude 7000 ft MSL. While on vector, crew observed aircraft target on TCASII approaching from east at same altitude heading wbound. Crew discussed potential evasive action. Crew attempted to call ATC to inquire about wbound aircraft and to state that we were turning right to avoid target. There was no response from ATC. We started right turn and reduced power for possible descent. TCASII then issued TA. We started down to avoid conflict when TCASII RA was issued, descend, descend, now. Nose over and speed brakes deployed to comply with TCASII advisory command. The TCASII then stated increase descent. At this point the aircraft in conflict, a B737, was in visual contact, and clearly a threat. We descended to 5200 ft MSL and leveled at 5800 ft MSL to avoid traffic and comply with TCASII commands. I stated to ATC our TCASII conflict, and our actions based on TCASII RA. I stated that based on the TA, we had descended and leveled at 5800 ft MSL. I asked ATC what altitude he wanted us level at. He stated 5000 ft MSL. I stated to controller that we were level at 7000 ft MSL, 250 KTS and on assigned 150 degree heading prior to the conflict and asked where the other aircraft came from. He responded that the B737 was being vectored to runway 19R by another controller and he would not comment on any other statements. We landed on runway 19L mci. Supplemental information from acn 445327: corrective action: ATC to follow their procedures. Having 2 aircraft heading in opposite directions at the same altitude within the same approach corridor/sector and talking to separate controllers does not seem to be very safe. Contributing factors: the 2 aircraft in the same area controled by 2 different controllers. Also, trying to get a particular aircraft to a specific runway (left or right side) for ease of gate access, decrease taxi times or ramp congestion. Need to have a method or procedure set in motion for this if you try to accommodate for the purpose runway selection.
Original NASA ASRS Text
Title: 2 ACR'S MEET HEAD ON COMPLIMENTS OF ATC. TCASII RA AND SEE AND BE SEEN PREVENT DISASTER. CTLR WOULD NOT DISCUSS IT.
Narrative: ACFT ON 150 DEG HDG, MCI APCH CTL BEING VECTORED FOR VISUAL APCH TO RWY 19L MCI. AIRSPD 250 KIAS ALT 7000 FT MSL. WHILE ON VECTOR, CREW OBSERVED ACFT TARGET ON TCASII APCHING FROM E AT SAME ALT HEADING WBOUND. CREW DISCUSSED POTENTIAL EVASIVE ACTION. CREW ATTEMPTED TO CALL ATC TO INQUIRE ABOUT WBOUND ACFT AND TO STATE THAT WE WERE TURNING R TO AVOID TARGET. THERE WAS NO RESPONSE FROM ATC. WE STARTED R TURN AND REDUCED PWR FOR POSSIBLE DSCNT. TCASII THEN ISSUED TA. WE STARTED DOWN TO AVOID CONFLICT WHEN TCASII RA WAS ISSUED, DSND, DSND, NOW. NOSE OVER AND SPD BRAKES DEPLOYED TO COMPLY WITH TCASII ADVISORY COMMAND. THE TCASII THEN STATED INCREASE DSCNT. AT THIS POINT THE ACFT IN CONFLICT, A B737, WAS IN VISUAL CONTACT, AND CLRLY A THREAT. WE DSNDED TO 5200 FT MSL AND LEVELED AT 5800 FT MSL TO AVOID TFC AND COMPLY WITH TCASII COMMANDS. I STATED TO ATC OUR TCASII CONFLICT, AND OUR ACTIONS BASED ON TCASII RA. I STATED THAT BASED ON THE TA, WE HAD DSNDED AND LEVELED AT 5800 FT MSL. I ASKED ATC WHAT ALT HE WANTED US LEVEL AT. HE STATED 5000 FT MSL. I STATED TO CTLR THAT WE WERE LEVEL AT 7000 FT MSL, 250 KTS AND ON ASSIGNED 150 DEG HDG PRIOR TO THE CONFLICT AND ASKED WHERE THE OTHER ACFT CAME FROM. HE RESPONDED THAT THE B737 WAS BEING VECTORED TO RWY 19R BY ANOTHER CTLR AND HE WOULD NOT COMMENT ON ANY OTHER STATEMENTS. WE LANDED ON RWY 19L MCI. SUPPLEMENTAL INFO FROM ACN 445327: CORRECTIVE ACTION: ATC TO FOLLOW THEIR PROCS. HAVING 2 ACFT HEADING IN OPPOSITE DIRECTIONS AT THE SAME ALT WITHIN THE SAME APCH CORRIDOR/SECTOR AND TALKING TO SEPARATE CTLRS DOES NOT SEEM TO BE VERY SAFE. CONTRIBUTING FACTORS: THE 2 ACFT IN THE SAME AREA CTLED BY 2 DIFFERENT CTLRS. ALSO, TRYING TO GET A PARTICULAR ACFT TO A SPECIFIC RWY (L OR R SIDE) FOR EASE OF GATE ACCESS, DECREASE TAXI TIMES OR RAMP CONGESTION. NEED TO HAVE A METHOD OR PROC SET IN MOTION FOR THIS IF YOU TRY TO ACCOMMODATE FOR THE PURPOSE RWY SELECTION.
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.