 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier captain departing phx was advised of traffic ahead and acquired the traffic visually. The reporter continued the climb and turned behind conflicting traffic.
| Attributes | |
| ACN | 871715 |
| Time | |
| Date | 201001 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PHX.Airport |
| State Reference | AZ |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Descent |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural FAR |
Narrative:
After takeoff from 7L in phx; tower advised not to switch to departure as he detected a traffic conflict in front of our flight path. At the time we were in a high rate of climb (3-4k ft/min). We immediately acquired a visual on the traffic. The conflicting traffic was 12 o-clock about 1/2 mile; passing right to left and diving rapidly through our altitude. Simultaneously; the TCAS called 'adjust vertical speed'. As the pilot flying; I maintained a visual with the conflicting aircraft and evaded by executing a right turn (into the path of the conflicting aircraft); while continuing the climb; based on the conflicting traffic descending and passing to the left. No unusual attitude or angle of bank was required in the evasion maneuver. The evasion was mild enough to the point of there not being any questioning from flight attendants or passengers as to what had occurred. No further incident and the flight continued uneventfully. ATC stated that they would attempt to find out who the conflicting aircraft was. Conflict aircraft in class B and should not have been there.I don't believe anything could have been done differently to prevent this incident from our perspective. From the perspective of the conflicting aircraft; better understanding of flight rules.
Original NASA ASRS Text
Title: An air carrier Captain departing PHX was advised of traffic ahead and acquired the traffic visually. The reporter continued the climb and turned behind conflicting traffic.
Narrative: After takeoff from 7L in PHX; Tower advised not to switch to departure as he detected a traffic conflict in front of our flight path. At the time we were in a high rate of climb (3-4K ft/min). We immediately acquired a visual on the traffic. The conflicting traffic was 12 O-Clock about 1/2 mile; passing right to left and diving rapidly through our altitude. Simultaneously; the TCAS called 'Adjust Vertical Speed'. As the Pilot Flying; I maintained a visual with the conflicting aircraft and evaded by executing a right turn (into the path of the conflicting aircraft); while continuing the climb; based on the conflicting traffic descending and passing to the left. No unusual attitude or angle of bank was required in the evasion maneuver. The evasion was mild enough to the point of there not being any questioning from flight attendants or passengers as to what had occurred. No further incident and the flight continued uneventfully. ATC stated that they would attempt to find out who the conflicting aircraft was. Conflict Aircraft in Class B and should not have been there.I don't believe anything could have been done differently to prevent this incident from our perspective. From the perspective of the conflicting aircraft; better understanding of flight rules.
Data retrieved from NASA's ASRS site as of April 2012 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.