Unstable approach — N278K
KPUB · 122026-08-05 00:38 UTC· KSBM → KPUB· THIENES ENGINEERING INC· C25A
N278K (Thienes Engineering) was operating from KSBM to KPUB on 2026-08-05. SkyMeter detected a low approach-stability score at Pueblo Memorial Airport (KPUB) on runway 12 at 00:38 UTC. Trace data at the event: 5804 ft AGL, 148 kt GS. METAR at the time reported 15 kt wind, 4 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)- HAZARDS6/9566 2026-07-28 17:15Z – 2026-08-11 04:00Z SFC–10,000 ft
33NM SW PHILIP, SD, Tuesday, July 28, 2026 through Tuesday, August 11, 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 12
- 5804 ft AGL at event
- 148 kt ground speed
- 0 fpm vertical
- 15 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- METAR KPUB 151853Z 07008KT 10SM BKN037 20/09 A3028 RMK AO2 SLP195 T02000094
Flight context
- N278K
- Thienes Engineering
- C25A
- KSBM → KPUB
- 2026-08-05 00:38 UTC
- KPUB runway 12
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