2010-06 · NASA ASRS report 895247
ZLA reporters described a possible loss of separation event involving a stealth aircraft and LAX inbound traffic; the reporters noting the complexity/confusion when trying to work a stealth aircraft in Class A airspace lacking reliable primary RADAR information.
An F22 with no transponder primary only RADAR identified. Lost primary target just south of arrival corridor for LAX. I told aircraft 'RADAR contact lost'; and had aircraft track inbound on PMD 100R and report 100 miles out. I then asked the aircraft if there was anyway to enhance RADAR detection as the aircraft is a stealth fighter. Pilot advised only way that could be done would lose the aircraft radios. I didn't think that was a good idea so I didn't do that. Asked aircraft position pilot responded PMD 100/107. I asked pilot to report 75 miles out as this would be clear of my arrivals which were stopped above them at FL290. I asked for an overhead which was provided. I got another report at 78 miles and my arrival aircraft reported and F-22 off to the right of them. I instructed the F22 to join the PMD 70 DME ARC and to arc north to the PMD 075R and track inbound on that radial. I did this to get aircraft to the north for Sector 37 inbound traffic to LAX also. Overhead said that information was passed to Sector 37 I then asked the F22 if they were established on the arc. Pilot said I gave it to them a bit late but that he was on the 69 DME ARC. Sector 37 then asked to talk to the F22 so I switched the aircraft to their frequency. I was so far behind at this point I took awhile to catch back up. I had approx 10-12 aircraft I was working both climbing and descending. It was very stressful situation. It is unsafe situation when the aircraft is stealth or maybe our RADAR coverage wasn't very good. Recommendation; not take primary only aircraft in Class A air especially if they are stealth.
The Controller in Charge (CIC) told me that a F22 stealth aircraft had lost its transponder and was headed my way at FL280. The CIC also told me that the sector that was currently working the aircraft was getting a strong primary target; but this sector was about three sectors ahead of me. I was confused about how we were receiving a primary target on a stealth aircraft and questioned the CIC; I also looked for the primary target and could not find one. I then received coordination from Sector 37 stating that the aircraft was level at FL280 and on the PMD 100 radial about 78 NM out from PMD. Sector 37 was training on the D-Side and there seemed to be a lot of confusion about what was happening with the aircraft and all of their LAX arrivals. Sector 37 then shipped the aircraft to me while the data tag was associated with a primary target well inside of my airspace. When the pilot checked on I asked for a position report and the pilot stated he/she was 54 NM southeast of PMD; which put the aircraft back into 37's Airspace. I then moved the data tag to a more appropriate location and called Sector 37 to let them know where the aircraft currently was. It was at this time that I noticed several limited data blocks that were descending through FL280 in the area where the F22 pilot had just reported. I then asked the pilot for several more position reports; handed the aircraft off to Joshua Approach and used NON-RADAR separation until I had conformation that the aircraft had exited my airspace. I was told later that the Sector 39 Controller had issued some sort of DME ARC but had not coordinated with myself or Sector 37. Recommendation; it seemed apparent that some of the Controllers involved were not familiar with NON-RADAR procedures and became very confused. I was also confused on how to handle the situation. Maybe some more training on these procedures would have helped.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.