Diversion — AAY1194
KCZG · 032026-07-29 21:41 UTC· KSFB → KCZG· SUNRISE ASSET MANAGEMENT LLC· B38M
AAY1194 (Sunrise Asset Management) was operating from KSFB to KELM (Elmira Corning Regional Airport) on 2026-07-29. SkyMeter detected a diversion to Tri Cities Airport (KCZG) on runway 03 at 21:41 UTC. Peak cruise altitude FL392, turnaround area near Moore, US. Approach stability score: 28/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 8 kt wind, 7 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft
2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/8779 2026-07-26 18:03Z – 2026-08-02 01:30Z SFC–1,300 ft
16NM NE LAKE CITY, FL, Sunday, July 26, 2026 through Sunday, August 2, 2026 UTC
View FAA NOTAM → - SECURITY6/8418 2026-07-27 12:30Z – 2026-08-01 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, July 27, 2026 through Saturday, August 1, 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 03
- 827 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 28/100
- 8 kt wind
- 7 kt crosswind component
Flight context
- AAY1194
- Sunrise Asset Management
- B38M
- KSFB → KCZG
- 2026-07-29 21:41 UTC
- KCZG runway 03
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