37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1069852 |
Time | |
Date | 201302 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | BKL.Airport |
State Reference | OH |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Beechjet 400 |
Operating Under FAR Part | Part 135 |
Flight Phase | Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | Traffic Collision Avoidance System (TCAS) |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Conflict Airborne Conflict Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
After takeoff we were on an assigned heading of approximately 030 degrees; level at 2;000 feet and in IMC. The sic was hand flying the aircraft at this time. Departure controller then gave us a turn to 130 degrees and a climb to 3;000 feet. Shortly thereafter our controller told us of traffic at our 2 o'clock position. We were in our turn and just beginning our climb to 3;000 feet. Our controller then told us the traffic was at 2;400 feet. We spotted our traffic on TCAS at about twelve o'clock; within 1-2 miles; and 200 feet above us. Simultaneous to my telling the sic to increase our rate of climb and turn; he had already added power and pitched up. He also increased his rate of turn and passed the 130 degrees assigned in order to go to the right of the traffic. Once above and clear of the traffic he began a rapid push over to stop his climb at 3;000 feet; but could only stop his climb at 3;400 feet without causing items to fly upwards. Our controller then came up and said he showed us at 3;400 feet and told us to descend to 3;000 feet. I informed him that we had to climb rapidly to avoid traffic and that we were in the process of descending to 3;000 feet and turning back to a heading of 130 degrees. Our flight thereafter proceeded normally. Our passengers did comment on our rapid pull up; followed by our rapid push over. Upon landing we explained what had occurred and they were quite satisfied with our explanation. No injuries were suffered. I advised maintenance control that; given the situation; we were at a loss to understand why our TCAS system failed to give us a TA or an RA before we took action. If the controller knew the traffic was at 2;400 feet and our TCAS system showed him 200 feet above while we were climbing and turning into him; why didn't we receive alerts? Maintenance had me collar and MEL the TCAS system and they were going to have it checked. I do not see how we could have anticipated nor prevented an air traffic controller from turning and climbing our aircraft into traffic when that traffic was unknown to us before our turn and climb. I do recommend that during all takeoffs that the mfd range rings in the mapping mode be put into the lowest available range. That would limit the traffic shown to only aircraft that could potentially be in conflict with it.
Original NASA ASRS Text
Title: A BE-400 flight crew in IMC; cleared to climb and given a turn vector; took evasive action to avoid pop-up traffic shown by TCAS as 200 feet above them and between one and two miles away. While doing so they exceeded their assigned heading and altitude. Their TCAS provided neither TA nor RA warnings.
Narrative: After takeoff we were on an assigned heading of approximately 030 degrees; level at 2;000 feet and in IMC. The SIC was hand flying the aircraft at this time. Departure Controller then gave us a turn to 130 degrees and a climb to 3;000 feet. Shortly thereafter our Controller told us of traffic at our 2 o'clock position. We were in our turn and just beginning our climb to 3;000 feet. Our Controller then told us the traffic was at 2;400 feet. We spotted our traffic on TCAS at about twelve o'clock; within 1-2 miles; and 200 feet above us. Simultaneous to my telling the SIC to increase our rate of climb and turn; he had already added power and pitched up. He also increased his rate of turn and passed the 130 degrees assigned in order to go to the right of the traffic. Once above and clear of the traffic he began a rapid push over to stop his climb at 3;000 feet; but could only stop his climb at 3;400 feet without causing items to fly upwards. Our Controller then came up and said he showed us at 3;400 feet and told us to descend to 3;000 feet. I informed him that we had to climb rapidly to avoid traffic and that we were in the process of descending to 3;000 feet and turning back to a heading of 130 degrees. Our flight thereafter proceeded normally. Our passengers did comment on our rapid pull up; followed by our rapid push over. Upon landing we explained what had occurred and they were quite satisfied with our explanation. No injuries were suffered. I advised Maintenance Control that; given the situation; we were at a loss to understand why our TCAS system failed to give us a TA or an RA before we took action. If the Controller knew the traffic was at 2;400 feet and our TCAS system showed him 200 feet above while we were climbing and turning into him; why didn't we receive alerts? Maintenance had me collar and MEL the TCAS system and they were going to have it checked. I do not see how we could have anticipated nor prevented an Air Traffic Controller from turning and climbing our aircraft into traffic when that traffic was unknown to us before our turn and climb. I do recommend that during all takeoffs that the MFD range rings in the mapping mode be put into the lowest available range. That would limit the traffic shown to only aircraft that could potentially be in conflict with it.
Data retrieved from NASA's ASRS site as of July 2013 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.