Unstable approach — TKR10
KRDM · 292026-07-16 02:12 UTC· KBOI → KRDM· NEPTUNE AVIATION SERVICES INC· B462
TKR10 (Neptune Aviation Services) was operating from KBOI to KRDM on 2026-07-16. SkyMeter detected a low approach-stability score at Roberts Field (KRDM) on runway 29 at 02:12 UTC. Trace data at the event: 4153 ft AGL, 131 kt GS. METAR at the time reported 13 kt wind, 10 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/4158 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7869 2026-07-09 11:07Z – 2026-07-21 05:59Z SFC–400 ft
Meridian, ID
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 29
- 4153 ft AGL at event
- 131 kt ground speed
- 0 fpm vertical
- 13 kt wind
- 10 kt crosswind component
- 16,093 m visibility
- KRDM 162256Z 33011KT 10SM SCT041 19/07 A3008
Flight context
- TKR10
- Neptune Aviation Services
- B462
- KBOI → KRDM
- 2026-07-16 02:12 UTC
- KRDM runway 29
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