Diversion — AMF1941
KONT · 26L2026-08-08 01:51 UTC· KBFL → KONT· UAS TRANSERVICES INC· SW4
AMF1941 (UAS Transervices) was operating from KBFL to KBUR (Bob Hope Airport) on 2026-08-08. SkyMeter detected a diversion to Ontario International Airport (KONT) on runway 26L at 01:51 UTC. Peak altitude 11,874 ft, turnaround area near Lancaster, US. Approach stability score: 82/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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/2267 2026-08-05 18:05Z – 2026-08-08 04:00Z SFC–9,000 ft
27NM S BAKERSFIELD, CA, Wednesday, August 5, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/2489 2026-08-06 02:15Z – 2026-08-19 04:00Z SFC–9,000 ft
27NM S BAKERSFIELD, CA, Thursday, August 6, 2026 through Wednesday, August 19, 2026 UTC
View FAA NOTAM → - HAZARDS6/2916 2026-08-08 01:45Z – 2026-08-15 05:00Z SFC–6,000 ft
25NM S BAKERSFIELD, CA, Saturday, August 8, 2026 through Saturday, August 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
- Runway 26L
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 82/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KONT 151353Z 23004KT 10SM FEW130 SCT200 19/17 A3007 RMK AO2 SLP170 T01890167 $
Flight context
- AMF1941
- UAS Transervices
- SW4
- KBFL → KONT
- 2026-08-08 01:51 UTC
- KONT runway 26L
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