Diversion — AMF7183
KJVY · 182026-08-29 14:55 UTC· KFTW → KJVY· UAS TRANSERVICES INC· SW4
AMF7183 (UAS Transervices) was operating from KFTW to KBED (Laurence G Hanscom Field) on 2026-08-29. SkyMeter detected a diversion to Clark Regional Airport (KJVY) on runway 18 at 14:55 UTC. Peak altitude 15,943 ft, turnaround area near Independence, US. Approach stability score: 41/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 2 kt wind, 2 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft
Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC
View FAA NOTAM → - HAZARDS6/8103 2026-08-26 12:00Z – 2026-09-09 02:00Z SFC–4,000 ft
21NM NW BROKEN BOW, OK, Wednesday, August 26, 2026 through Wednesday, September 9, 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 18
- 461 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 41/100
- 2 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- METAR KJVY 151735Z AUTO VRB05KT 10SM CLR 32/21 A3014 RMK AO2
Flight context
- AMF7183
- UAS Transervices
- SW4
- KFTW → KJVY
- 2026-08-29 14:55 UTC
- KJVY runway 18
All events on this flight
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