VTM679 had departed KOAK on 2026-03-04. SkyMeter detected a rejectedtakeoff at Metropolitan Oakland International Airport (KOAK) on runway 12 at 17:28 UTC. Trace data at the event: 8 ft AGL, 62 kt GS, 0 fpm vertical. METAR at the time reported 8 kt wind, 4 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/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft
Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local
View FAA NOTAM → - SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft
Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft
Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 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 12
- 8 ft AGL at event
- 62 kt ground speed
- 0 fpm vertical
- 8 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KOAK 161053Z 20009KT 10SM FEW006 BKN020 17/13 A2991 RMK AO2 SLP126 T01670128
Flight context
- VTM679
- CRJ2
- 2026-03-04 17:28 UTC
- KOAK runway 12
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