Rejected takeoff — OPN63

KGAI · 32

2026-01-12 06:46 UTC· KGAI KALB· KILOLIMA3 LLC· SF50

OPN63 (Kilolima3) was operating from KGAI to KALB on 2026-01-12. SkyMeter detected a rejectedtakeoff at Montgomery County Airpark (KGAI) on runway 32 at 06:46 UTC. Trace data at the event: 518 ft AGL, 71 kt GS. Approach stability score: 86/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 10 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)
  • 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 →

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 32
  • 518 ft AGL at event
  • 71 kt ground speed
  • 0 fpm vertical
  • Approach stability 86/100
  • 10 kt wind
  • 2 kt crosswind component
  • 16,093 m visibility
  • METAR KGAI 160956Z AUTO 13003KT 10SM CLR 16/16 A3036 RMK AO2 SLP290 T01560156

Flight context

  • OPN63
  • Kilolima3
  • SF50
  • KGAI → KALB
  • 2026-01-12 06:46 UTC
  • KGAI runway 32

All events on this flight

Rejected takeoff 06:46:21 UTC · KGAI runway 32 · 518 ft AGL · 71 kt GS
Rejected takeoff 06:46:21 UTC · KGAI runway 32 · 518 ft AGL · 71 kt GS
Rejected takeoff 06:46:21 UTC · KGAI runway 32 · 518 ft AGL · 71 kt GS
Rejected takeoff 06:46:21 UTC · KGAI runway 32 · 518 ft AGL · 71 kt GS
Rejected takeoff 06:46:21 UTC · KGAI runway 32 · 518 ft AGL · 71 kt GS
Rejected takeoff 06:46:21 UTC · KGAI runway 32 · 518 ft AGL · 71 kt GS

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· KGAI