BOXER39 was operating from KDLF to KDLF on 2026-09-03. SkyMeter recorded a 7600 transponder transmission at 20:15 UTC. Code 7600 indicates a lost-comms / NORDO state; brief transmissions are often transient radio or transponder issues that resolve without crew action. Trace data at the event: 4859 ft AGL, 338 kt GS. Approach stability score: 84/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 11 kt wind, 8 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft
SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - HAZARDS6/9244 2026-08-30 20:00Z – 2026-09-06 02:00Z SFC–6,000 ft
12NM NW ROCKSPRINGS, TX, Sunday, August 30, 2026 through Sunday, September 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/9262 2026-08-31 13:00Z – 2026-09-15 02:00Z SFC–6,000 ft
12NM NW ROCKSPRINGS, TX, Monday, August 31, 2026 through Tuesday, September 15, 2026 UTC
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- 4859 ft AGL at event
- 338 kt ground speed
- 0 fpm vertical
- Approach stability 84/100
- 11 kt wind
- 8 kt crosswind component
Flight context
- BOXER39
- T38
- KDLF → KDLF
- 2026-09-03 20:15 UTC
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data