Unstable approach — LFG223
KFOK · 332026-07-19 18:19 UTC· CYEG → KFOK· JAYDAK LLC· CL30
LFG223 (Jaydak) was operating from CYEG to KFOK on 2026-07-19. SkyMeter detected a low approach-stability score at Francis S Gabreski Airport (KFOK) on runway 33 at 18:19 UTC. Trace data at the event: 1179 ft AGL, 120 kt GS. Approach stability score: 36/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 12 kt wind, 1 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4348 2026-03-08 07:00Z – 2026-11-01 06:59Z SFC–2,400 ft
GRAND FORKS AFB, ND, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/9462 2026-06-24 04:00Z – 2026-07-21 03:29Z SFC–400 ft
Montclair, NJ, Wednesday, June 24, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/5591 2026-07-15 17:00Z – 2026-07-20 04:59Z SFC–400 ft
Hammond, IN, Wednesday, July 15, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - SECURITY6/5841 2026-07-16 13:00Z – 2026-07-27 05:59Z SFC–400 ft
Cheyenne, WY, Thursday, July 16, 2026 through Sunday, July 26, 2026 Local
View FAA NOTAM → - SECURITY6/5882 2026-07-17 16:30Z – 2026-07-20 04:00Z SFC–400 ft
MINNEAPOLIS, MN, Friday, July 17, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - VIP6/6037 2026-07-17 22:30Z – 2026-07-19 18:45Z SFC–17,999 ft
Bedminster, NJ, Friday, July 17, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - VIP6/6038 2026-07-17 22:30Z – 2026-07-19 18:45Z SFC–17,999 ft
Bedminster, NJ, Friday, July 17, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - AIR SHOWS/SPORTS6/5171 2026-07-18 16:00Z – 2026-07-19 21:30Z SFC–16,000 ft
Sioux Falls, SD, Saturday, July 18, 2026 through Sunday, July 19, 2026 UTC
View FAA NOTAM → - SECURITY6/6102 2026-07-19 16:00Z – 2026-07-20 01:00Z SFC–3,000 ft
East Rutherford, NJ, Sunday, July 19, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/5201 2026-07-19 17:00Z – 2026-07-20 04:30Z SFC–400 ft
madison, WI, Sunday, July 19, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - VIP6/6103 2026-07-19 17:00Z – 2026-07-20 00:01Z SFC–17,999 ft
East Rutherford, NJ, Sunday, July 19, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - VIP6/6104 2026-07-19 17:00Z – 2026-07-20 00:01Z SFC–17,999 ft
East Rutherford, NJ, Sunday, July 19, 2026 through Sunday, July 19, 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 33
- 1179 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 36/100
- 12 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KFOK 150253Z 00000KT 10SM SCT060 OVC110 21/20 A3010 RMK AO2 SLP193 60000 T02110200 51014
Flight context
- LFG223
- Jaydak
- CL30
- CYEG → KFOK
- 2026-07-19 18:19 UTC
- KFOK runway 33
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