Diversion — ASP844
KTEB · 062026-08-28 20:07 UTC· CYUL → KTEB· AIRSPRINT INC.· E545
ASP844 (Airsprint) was operating from CYUL to CYYZ (Lester B. Pearson International Airport) on 2026-08-28. SkyMeter detected a diversion to Teterboro Airport (KTEB) on runway 06 at 20:07 UTC. Peak cruise altitude FL288, turnaround area near Hagaman, US. Approach stability score: 76/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 6 kt wind, 6 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 → - SECURITY6/7002 2026-08-24 13:00Z – 2026-09-13 07:00Z SFC–1,000 ft
Flushing, NY, Monday, August 24, 2026 through Sunday, September 13, 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 06
- 8 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 76/100
- 6 kt wind
- 6 kt crosswind component
- 16,093 m visibility
- KTEB 072151Z 32005KT 10SM CLR 26/10 A3012 RMK AO2 SLP200 T02610100 $
Flight context
- ASP844
- Airsprint
- E545
- CYUL → KTEB
- 2026-08-28 20:07 UTC
- KTEB runway 06
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