Return to field — RLI526
KDXR · 262026-08-14 14:54 UTC· KDXR → KDXR· N525RE LLC· C25B
RLI526 (N525re) was operating from KDXR to KDXR (Danbury Municipal Airport) on 2026-08-14. SkyMeter detected a return to field at Danbury Municipal Airport (KDXR) on runway 26 at 14:54 UTC. Peak cruise altitude FL450, turnaround area near Welland, CA. 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)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/4915 2026-08-14 15:55Z – 2026-08-14 22:20Z SFC–2,000 ft
Garden City, NY, Friday, August 14, 2026 Local
View FAA NOTAM → - VIP6/4487 2026-08-14 17:15Z – 2026-08-14 21:15Z SFC–17,999 ft
Garden City, NY, Friday, August 14, 2026 Local
View FAA NOTAM → - VIP6/4488 2026-08-14 17:15Z – 2026-08-14 21:15Z SFC–17,999 ft
Garden City, NY, Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/2888 2026-08-14 18:00Z – 2026-08-15 03:30Z SFC–400 ft
EAST RUTHERFORD, NJ, Friday, August 14, 2026 through Friday, August 14, 2026 Local
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 26
- 45061 ft AGL at event
- 538 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- METAR KDXR 152353Z 17006KT 10SM CLR 16/11 A3037 RMK AO2 SLP282 T01610106 10206 20161 51001
Flight context
- RLI526
- N525re
- C25B
- KDXR → KDXR
- 2026-08-14 14:54 UTC
- KDXR runway 26
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