37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 258084 |
Time | |
Date | 199311 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : jli |
State Reference | CA |
Altitude | msl bound lower : 16500 msl bound upper : 17500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zla |
Operator | common carrier : air carrier |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 135 |
Flight Phase | cruise other |
Flight Plan | IFR |
Aircraft 2 | |
Operator | other |
Make Model Name | Military Transport |
Operating Under FAR Part | other : other |
Flight Phase | climbout : intermediate altitude cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 7000 flight time type : 200 |
ASRS Report | 258084 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 6000 flight time type : 2000 |
ASRS Report | 258153 |
Events | |
Anomaly | conflict : nmac non adherence : far other anomaly other |
Independent Detector | other controllera other flight crewa |
Resolutory Action | flight crew : took evasive action |
Consequence | Other |
Miss Distance | horizontal : 0 vertical : 500 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
ZLA called our traffic at 10 O'clock 5 mi, however, altitude and direction were unreadable. We asked to verify the traffic was level at 16500 ft and were informed it was 16500 ft climbing. We then spotted traffic in a right turn at 10-11 O'clock. Appeared to be turning swbound and converging. We then immediately initiated descent. Aircraft passed overhead with approximately 500 ft vertical separation. We were informed our traffic had visual with us, however, did not appear to attempt any evasive action. Supplemental information from acn 258153: we saw the traffic, but were unable to see which way he was turning and if he was climbing or not. The other aircraft rolled out on a heading that would have resulted in colliding with us. 'Military call sign' also said they had us in sight. Since 'military call sign' had us in sight, why did that idiot roll out on a collision course?
Original NASA ASRS Text
Title: AN ACR LTT AND A MIL HVT HAD AN NMAC.
Narrative: ZLA CALLED OUR TFC AT 10 O'CLOCK 5 MI, HOWEVER, ALT AND DIRECTION WERE UNREADABLE. WE ASKED TO VERIFY THE TFC WAS LEVEL AT 16500 FT AND WERE INFORMED IT WAS 16500 FT CLBING. WE THEN SPOTTED TFC IN A R TURN AT 10-11 O'CLOCK. APPEARED TO BE TURNING SWBOUND AND CONVERGING. WE THEN IMMEDIATELY INITIATED DSCNT. ACFT PASSED OVERHEAD WITH APPROX 500 FT VERT SEPARATION. WE WERE INFORMED OUR TFC HAD VISUAL WITH US, HOWEVER, DID NOT APPEAR TO ATTEMPT ANY EVASIVE ACTION. SUPPLEMENTAL INFO FROM ACN 258153: WE SAW THE TFC, BUT WERE UNABLE TO SEE WHICH WAY HE WAS TURNING AND IF HE WAS CLBING OR NOT. THE OTHER ACFT ROLLED OUT ON A HDG THAT WOULD HAVE RESULTED IN COLLIDING WITH US. 'MIL CALL SIGN' ALSO SAID THEY HAD US IN SIGHT. SINCE 'MIL CALL SIGN' HAD US IN SIGHT, WHY DID THAT IDIOT ROLL OUT ON A COLLISION COURSE?
Data retrieved from NASA's ASRS site as of July 2007 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.