Rejected takeoff — EJA940
KIAD · 01R2026-05-30 12:21 UTC· KIAD → KSRQ· NETJETS SALES INC, AIRGO LLC, B&C CAPITAL SERVICES LLC, BROCKWAY· C68A
EJA940 (Netjets Sales) was operating from KIAD to KSRQ on 2026-05-30. SkyMeter detected a rejectedtakeoff at Washington Dulles International Airport (KIAD) on runway 01R at 12:21 UTC. Trace data at the event: 272 ft AGL, 110 kt GS, 0 fpm vertical. Approach stability score: 85/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 7 kt wind, 3 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/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft
Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/2992 2026-05-30 11:20Z – 2026-05-30 15:30Z SFC–180 ft
Cape Canaveral, FL, Saturday, May 30, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/2995 2026-05-30 11:20Z – 2026-05-30 15:30Z SFC–180 ft
Cape Canaveral, FL, Saturday, May 30, 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 01R
- 272 ft AGL at event
- 110 kt ground speed
- 0 fpm vertical
- Approach stability 85/100
- 7 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KIAD 170630Z AUTO 13004KT 10SM CLR 21/19 A3026 RMK T02100190 MADISHF
Flight context
- EJA940
- Netjets Sales
- C68A
- KIAD → KSRQ
- 2026-05-30 12:21 UTC
- KIAD runway 01R
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