 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-700 flight crew reported airborne conflict and a TCAS TA in climb to FL380. Captain speculated either ATC error or readback/hearback contributed to the event.
| Attributes | |
| ACN | 1083449 |
| Time | |
| Date | 201304 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZME.ARTCC |
| State Reference | TN |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Experience | Flight Crew Last 90 Days 212 |
| Person 2 | |
| Function | Pilot Flying First Officer |
| Experience | Flight Crew Last 90 Days 269 Flight Crew Type 5000 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
Flight requested climb from FL360 to FL380. Aircraft was on division line between [two ATC] centers. Center advised a short delay. [Controller] subsequently cleared us to climb to FL380. Passing through FL365; flight crew detected traffic alert TA on map display and visually acquired traffic opposite direction at FL370 and at 10 o'clock position. Crew initiated right turn to increase separation and advised [center] of conflict. [Center] advised both aircraft to turn 30 degrees right immediately. Suspect loss of separation at altitude.crew suspects two possible causes of event. Most likely is a controller error by center. [Center] may not have correctly accounted for inbound other carrier's aircraft arriving from [adjacent] airspace. Another possibility is that crew took climb clearance from FL360 to FL380 that was intended for another aircraft and that the incorrect climb readback was not detected by center. A company flight number was also heard on center once we were handed off to new center.
Original NASA ASRS Text
Title: B737-700 flight crew reported airborne conflict and a TCAS TA in climb to FL380. Captain speculated either ATC error or readback/hearback contributed to the event.
Narrative: Flight requested climb from FL360 to FL380. Aircraft was on division line between [two ATC] Centers. Center advised a short delay. [Controller] subsequently cleared us to climb to FL380. Passing through FL365; flight crew detected Traffic Alert TA on map display and visually acquired traffic opposite direction at FL370 and at 10 o'clock position. Crew initiated right turn to increase separation and advised [Center] of conflict. [Center] advised both aircraft to turn 30 degrees right immediately. Suspect loss of separation at altitude.Crew suspects two possible causes of event. Most likely is a controller error by Center. [Center] may not have correctly accounted for inbound other carrier's aircraft arriving from [adjacent] airspace. Another possibility is that Crew took climb clearance from FL360 to FL380 that was intended for another aircraft and that the incorrect climb readback was not detected by Center. A Company Flight Number was also heard on Center once we were handed off to new Center.
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.