Return to field — N227SV

KCHA · 20

2026-09-25 21:08 UTC· KCHA → KCHA· ASSEMBLY POINT AVIATION INC· GLF4

N227SV (Assembly Point Aviation) had departed KCHA on 2026-09-25. SkyMeter detected a return to field at Lovell Field (KCHA) on runway 20 at 21:08 UTC. Peak cruise altitude FL448, turnaround area near Bath, US. Approach stability score: 87/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. 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)
  • UAS PUBLIC GATHERING6/7351 2026-08-27 12:00Z – 2026-10-13 03:00Z SFC–400 ft

    Timonium, MD, Thursday, August 27, 2026 through Tuesday, October 13, 2026 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/4133 2026-09-25 15:00Z – 2026-09-28 05:00Z SFC–400 ft

    Ocean City, MD, Friday, September 25, 2026 through Monday, September 28, 2026 UTC

    View FAA NOTAM →
  • VIP6/4933 2026-09-25 20:30Z – 2026-09-27 21:00Z SFC–4,999 ft

    Rockbridge, OH, Friday, September 25, 2026 through Sunday, September 27, 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 20
  • 44883 ft AGL at event
  • 486 kt ground speed
  • 0 fpm vertical
  • Approach stability 87/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • METAR KCHA 251353Z VRB04KT 10SM OVC025 20/16 A3019 RMK AO2 SLP217 T02000156

Flight context

  • N227SV
  • Assembly Point Aviation
  • GLF4
  • KCHA → KCHA
  • 2026-09-25 21:08 UTC
  • KCHA runway 20

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

SkyMeter · trace data observed via ADS-B· KCHA