37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1313923 |
Time | |
Date | 201511 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | DXR.Airport |
State Reference | CT |
Environment | |
Light | Dawn |
Aircraft 1 | |
Make Model Name | Dash 8-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | Climb |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Track / Heading All Types |
Miss Distance | Horizontal 0 Vertical 500 |
Narrative:
While in cruise; we noticed an airplane on TCAS several miles ahead of us and 2400 feet below us in a climb. We watched the airplane continue to climb directly ahead of us at our 12 o'clock position. Figuring the airplane would level out 1000 below us; we continued on course but kept a vigilant eye on the traffic. Immediately once the traffic passed through 1000 feet below us in a steady climb; we queried approach about traffic at our 12 o'clock and a mile or two and climbing. Once the traffic hit 400 feet below us and directly ahead of us; I didn't wait for ATC to respond but immediately turned off the autopilot and advised ATC we were making an immediate turn to the west. During ATC's then notification of the traffic; we received a TCAS RA with a 2000 feet per minute climb. We complied with the RA; and the traffic passed directly below us at 500 feet separation until we received the 'clear of conflict' notification.being given notice of the traffic earlier (or at any time) by ATC certainly would have helped. The next controller let us know that the traffic appeared to have just departed danbury and climbed right through our altitude; so maybe the controllers were not anticipating this traffic? TCAS and monitoring our instruments certainly came through for us.
Original NASA ASRS Text
Title: DHC8 Captain at cruise altitude experienced an airborne conflict with another aircraft climbing into their altitude. The reporter initiated a turn at about the same time ATC called the traffic and TCAS annunciated a climb RA.
Narrative: While in cruise; we noticed an airplane on TCAS several miles ahead of us and 2400 feet below us in a climb. We watched the airplane continue to climb directly ahead of us at our 12 o'clock position. Figuring the airplane would level out 1000 below us; we continued on course but kept a vigilant eye on the traffic. Immediately once the traffic passed through 1000 feet below us in a steady climb; we queried Approach about traffic at our 12 o'clock and a mile or two and climbing. Once the traffic hit 400 feet below us and directly ahead of us; I didn't wait for ATC to respond but immediately turned off the autopilot and advised ATC we were making an immediate turn to the west. During ATC's then notification of the traffic; we received a TCAS RA with a 2000 feet per minute climb. We complied with the RA; and the traffic passed directly below us at 500 feet separation until we received the 'Clear of Conflict' notification.Being given notice of the traffic earlier (or at any time) by ATC certainly would have helped. The next controller let us know that the traffic appeared to have just departed Danbury and climbed right through our altitude; so maybe the controllers were not anticipating this traffic? TCAS and monitoring our instruments certainly came through for us.
Data retrieved from NASA's ASRS site 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.