Rejected takeoff — EJA833
KIAD · 01C2026-07-26 16:21 UTC· KBDR → KACK· NETJETS SALES INC, BEP LOGISTICS LLC, CARUSO VENTURES LLC, CJC A· C700
EJA833 (Netjets Sales) was operating from KBDR to KACK on 2026-07-26. SkyMeter detected a rejectedtakeoff at Washington Dulles International Airport (KIAD) on runway 01C at 16:21 UTC. Trace data at the event: 272 ft AGL, 180 kt GS, 0 fpm vertical. Approach stability score: 45/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 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 → - VIP6/8425 2026-07-26 11:30Z – 2026-07-26 22:30Z SFC–9,999 ft
Sterling, VA, Sunday, July 26, 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 01C
- 272 ft AGL at event
- 180 kt ground speed
- 0 fpm vertical
- Approach stability 45/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KIAD 162352Z 16005KT 10SM FEW100 FEW250 26/19 A3028 RMK AO2 SLP250 T02560189 10294 20256 56004
Flight context
- EJA833
- Netjets Sales
- C700
- KBDR → KACK
- 2026-07-26 16:21 UTC
- KIAD runway 01C
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