 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The crew responded to an RA after departing okc while trying to check in with kansas city center.
| Attributes | |
| ACN | 1312373 |
| Time | |
| Date | 201511 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZKC.ARTCC |
| State Reference | KS |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Regional Jet 900 (CRJ900) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude |
Narrative:
Departing okc; assigned heading by departure 340 and climb 15;000. Course was intercepting per radial 195 to larko intersection which we were established on at the time of the event. Switched to kc center. Controller was busy; pm waited as he should for freq to clear before checking on. After about 1 minute roughly; traffic appeared on TCAS at same altitude. Captain made comment; I verfied and started looking. Found conflict aircraft at time of TA (not RA yet); we each made some comment about corrective action. At 'RA' I; pilot flying (PF) disconnected ap and started a aggressive climb to comply with TCAS guidance. I also started a bank away from conflicting traffic at auto-pilot disconnect to add seperation/basic human survival i.e. Don't hit another plane at 15;000 going +300 knots. After compling with TCAS RA; corrected back to assigned altitude and course. Pilot monitoring (pm) notified center; (which he had no clue nor did it seem like he cared that he almost had two planes get togther at 15;000 feet) and we were then given another altitude to climb to and the rest of flight went as planned. Conflict aircraft silhouette appeared to me as a twin prop who banked away from us as well.
Original NASA ASRS Text
Title: The crew responded to an RA after departing OKC while trying to check in with Kansas City Center.
Narrative: Departing OKC; assigned heading by departure 340 and climb 15;000. Course was intercepting PER radial 195 to LARKO intersection which we were established on at the time of the event. Switched to KC Center. Controller was busy; PM waited as he should for freq to clear before checking on. After about 1 minute roughly; traffic appeared on TCAS at same altitude. Captain made comment; I verfied and started looking. Found conflict aircraft at time of TA (not RA yet); we each made some comment about corrective action. At 'RA' I; Pilot Flying (PF) disconnected AP and started a aggressive climb to comply with TCAS guidance. I also started a bank away from conflicting traffic at auto-pilot disconnect to add seperation/basic human survival i.e. don't hit another plane at 15;000 going +300 knots. After compling with TCAS RA; corrected back to assigned altitude and course. Pilot Monitoring (PM) notified Center; (which he had no clue nor did it seem like he cared that he almost had two planes get togther at 15;000 feet) and we were then given another altitude to climb to and the rest of flight went as planned. Conflict aircraft silhouette appeared TO ME as a twin prop who banked away from us as well.
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.