Rejected takeoff — N926JC
KTEB · 62026-07-31 22:11 UTC· KTEB → ?· JCD LEASING LLC· F2TH
N926JC (JCD Leasing) had departed KTEB on 2026-07-31. SkyMeter detected a rejectedtakeoff at Teterboro Airport (KTEB) on runway 6 at 22:11 UTC. Trace data at the event: 0 ft AGL, 89 kt GS, 0 fpm vertical. METAR at the time reported 10 kt wind, 10 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/0567 2026-07-31 18:00Z – 2026-08-02 23:30Z SFC–2,000 ft
Morristown, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local
View FAA NOTAM → - VIP6/9922 2026-07-31 19:15Z – 2026-08-02 22:45Z SFC–17,999 ft
Bedminster, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local
View FAA NOTAM → - VIP6/9923 2026-07-31 19:15Z – 2026-08-02 22:45Z SFC–17,999 ft
Bedminster, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local
View FAA NOTAM → - VIP6/0695 2026-07-31 20:45Z – 2026-07-31 22:30Z SFC–17,999 ft
Morristown, NJ, Friday, July 31, 2026 Local
View FAA NOTAM → - VIP6/0696 2026-07-31 20:45Z – 2026-07-31 22:30Z SFC–17,999 ft
Morristown, NJ, Friday, July 31, 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 6
- 0 ft AGL at event
- 89 kt ground speed
- 0 fpm vertical
- 10 kt wind
- 10 kt crosswind component
- 16,093 m visibility
- KTEB 161451Z VRB06KT 10SM BKN095 22/15 A3037 RMK AO2 SLP283 60001 T02170150 53001 $
Flight context
- N926JC
- JCD Leasing
- F2TH
- 2026-07-31 22:11 UTC
- KTEB runway 6
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