Unstable approach — TKR168
KOGD · 342026-06-22 01:38 UTC· KCIC → KOGD· AERO-FLITE INC· RJ85
TKR168 (Aero-Flite) was operating from KCIC to KOGD on 2026-06-22. SkyMeter detected a low approach-stability score at Ogden Hinckley Airport (KOGD) on runway 34 at 01:38 UTC. Trace data at the event: 5526 ft AGL, 137 kt GS. METAR at the time reported 3 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/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft
BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft
SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local
View FAA NOTAM → - HAZARDS6/6827 2026-06-09 17:15Z – 2026-06-22 02:00Z SFC–10,000 ft
9NM SW TOOELE, UT, Tuesday, June 9, 2026 through Monday, June 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/6965 2026-06-10 14:00Z – 2026-06-22 03:00Z SFC–10,000 ft
9NM SW TOOELE, UT, Wednesday, June 10, 2026 through Monday, June 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/9269 2026-06-18 19:00Z – 2026-06-30 04:00Z SFC–11,000 ft
39NM NW MESQUITE, NV, Thursday, June 18, 2026 through Tuesday, June 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/9356 2026-06-20 13:00Z – 2026-07-03 04:00Z SFC–11,000 ft
46 NM NW MESQUITE, NV, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/9359 2026-06-20 13:00Z – 2026-07-03 04:00Z SFC–11,000 ft
39 NM NW MESQUITE, NV, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/9412 2026-06-20 17:53Z – 2026-07-03 04:00Z SFC–11,000 ft
27NM SW PROVO, UT, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/9457 2026-06-21 13:00Z – 2026-07-04 04:00Z SFC–12,000 ft
39 NM NW MESQUITE, NV, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9458 2026-06-21 13:00Z – 2026-07-04 04:00Z SFC–12,000 ft
37NM NW MESQUITE, NV, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9460 2026-06-21 14:00Z – 2026-07-04 04:00Z SFC–11,000 ft
27NM SW PROVO, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC
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 34
- 5526 ft AGL at event
- 137 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KOGD 100153Z 16015KT 10SM FEW110 24/02 A2977 RMK AO2 SLP031 T02390017
Flight context
- TKR168
- Aero-Flite
- RJ85
- KCIC → KOGD
- 2026-06-22 01:38 UTC
- KOGD runway 34
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