37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 539099 |
Time | |
Date | 200202 |
Day | Fri |
Place | |
Locale Reference | airport : ord.airport |
State Reference | IL |
Altitude | msl bound lower : 1600 msl bound upper : 2000 |
Aircraft 1 | |
Controlling Facilities | tower : ord.tower |
Operator | common carrier : air carrier |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : initial |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : ord.tower |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet CL65, Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach landing : go around |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 539099 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | non adherence : published procedure non adherence : required legal separation |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | controller : issued new clearance flight crew : took evasive action other |
Consequence | faa : investigated other |
Miss Distance | horizontal : 1500 vertical : 400 |
Supplementary | |
Problem Areas | FAA ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error Inter Facility Coordination Failure Intra Facility Coordination Failure |
Narrative:
We received the following clearance: fly 260 degree heading, cleared for takeoff runway 27L. During our takeoff roll, I heard the tower direct an aircraft to go around. The runway the go around aircraft was attempting to land on was not mentioned. While we were climbing on a 260 degree heading, the first officer stated tersely 'stop climb.' I lowered our nose and stopped climbing and asked what was up, to which he replied 'we have traffic.' I looked out his side window and saw the underside of an air carrier Y rj which was in a climbing tight right turn away from us going through a heading parallel to ours. He seemed just slightly above us. At no time did we receive a TCASII aural alert. The aircraft appeared to come within 1/2 mi by the first officer's estimation, but it looked closer -- perhaps 1/4 mi. We kept visual separation from the rj. The tower told us to turn left 220 degrees. We then saw a yellow TCASII target with an altitude readout of +400 ft on our nds that correlated to the rjs position. Our altitude was approximately 1600-2000 ft MSL. Given the position of the rj, I presume he was executing a missed approach to runway 14R. Our actions to avoid closure between our 2 aircraft were based on our visual sighting of the rj in the absence of TCASII or ATC guidance. Supplemental information from acn 539707: I looked up and saw an rj at our 2 O'clock position. He was a yellow circle on my TCASII screen and showing 400 ft above us. I guess the range was about 1/2 NM, and that was the closest point of approach. I called the traffic and told the captain to level off. Just then tower gave us a hard left turn to 200 degrees. We were too low for the TCASII to give us any traffic calls -- below 1100 ft AGL. I don't think they ever picked us up visually. Callback conversation with reporter acn 539099 revealed the following information: the conflicting aircraft was a CL65. The report was investigated by the air carrier safety department. Their report was turned over to the FAA at ord. They indicated controller training was being conducted. They indicated the B737 should never have been given takeoff clearance. Boeing has suppressed all aural TCASII warnings below 1100 ft radio altitude. This would account for the lack of TCASII aural warning. The captain was using the aircraft HUD for takeoff, so he had the outside environment already in sight through the HUD.
Original NASA ASRS Text
Title: B737 CREW AND AN ACR CL65 HAD LESS THAN LEGAL SEPARATION IN ORD CLASS B AIRSPACE.
Narrative: WE RECEIVED THE FOLLOWING CLRNC: FLY 260 DEG HDG, CLRED FOR TKOF RWY 27L. DURING OUR TKOF ROLL, I HEARD THE TWR DIRECT AN ACFT TO GO AROUND. THE RWY THE GAR ACFT WAS ATTEMPTING TO LAND ON WAS NOT MENTIONED. WHILE WE WERE CLBING ON A 260 DEG HDG, THE FO STATED TERSELY 'STOP CLB.' I LOWERED OUR NOSE AND STOPPED CLBING AND ASKED WHAT WAS UP, TO WHICH HE REPLIED 'WE HAVE TFC.' I LOOKED OUT HIS SIDE WINDOW AND SAW THE UNDERSIDE OF AN ACR Y RJ WHICH WAS IN A CLBING TIGHT R TURN AWAY FROM US GOING THROUGH A HDG PARALLEL TO OURS. HE SEEMED JUST SLIGHTLY ABOVE US. AT NO TIME DID WE RECEIVE A TCASII AURAL ALERT. THE ACFT APPEARED TO COME WITHIN 1/2 MI BY THE FO'S ESTIMATION, BUT IT LOOKED CLOSER -- PERHAPS 1/4 MI. WE KEPT VISUAL SEPARATION FROM THE RJ. THE TWR TOLD US TO TURN L 220 DEGS. WE THEN SAW A YELLOW TCASII TARGET WITH AN ALT READOUT OF +400 FT ON OUR NDS THAT CORRELATED TO THE RJS POS. OUR ALT WAS APPROX 1600-2000 FT MSL. GIVEN THE POS OF THE RJ, I PRESUME HE WAS EXECUTING A MISSED APCH TO RWY 14R. OUR ACTIONS TO AVOID CLOSURE BTWN OUR 2 ACFT WERE BASED ON OUR VISUAL SIGHTING OF THE RJ IN THE ABSENCE OF TCASII OR ATC GUIDANCE. SUPPLEMENTAL INFO FROM ACN 539707: I LOOKED UP AND SAW AN RJ AT OUR 2 O'CLOCK POS. HE WAS A YELLOW CIRCLE ON MY TCASII SCREEN AND SHOWING 400 FT ABOVE US. I GUESS THE RANGE WAS ABOUT 1/2 NM, AND THAT WAS THE CLOSEST POINT OF APCH. I CALLED THE TFC AND TOLD THE CAPT TO LEVEL OFF. JUST THEN TWR GAVE US A HARD L TURN TO 200 DEGS. WE WERE TOO LOW FOR THE TCASII TO GIVE US ANY TFC CALLS -- BELOW 1100 FT AGL. I DON'T THINK THEY EVER PICKED US UP VISUALLY. CALLBACK CONVERSATION WITH RPTR ACN 539099 REVEALED THE FOLLOWING INFO: THE CONFLICTING ACFT WAS A CL65. THE RPT WAS INVESTIGATED BY THE ACR SAFETY DEPT. THEIR RPT WAS TURNED OVER TO THE FAA AT ORD. THEY INDICATED CTLR TRAINING WAS BEING CONDUCTED. THEY INDICATED THE B737 SHOULD NEVER HAVE BEEN GIVEN TKOF CLRNC. BOEING HAS SUPPRESSED ALL AURAL TCASII WARNINGS BELOW 1100 FT RADIO ALT. THIS WOULD ACCOUNT FOR THE LACK OF TCASII AURAL WARNING. THE CAPT WAS USING THE ACFT HUD FOR TKOF, SO HE HAD THE OUTSIDE ENVIRONMENT ALREADY IN SIGHT THROUGH THE HUD.
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.