LOBO148 was operating from KNKT to KHRT on 2026-07-13. SkyMeter detected a low approach-stability score at Hurlburt Field (KHRT) on runway 36 at 17:31 UTC. Trace data at the event: 1153 ft AGL, 176 kt GS. Approach stability score: 59/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 4 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)- SECURITY6/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3991 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3998 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Atlanta, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4132 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/8212 2026-06-17 04:01Z – 2026-07-17 03:59Z SFC–400 ft
Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 2026 Local
View FAA NOTAM → - SECURITY6/7594 2026-07-08 16:07Z – 2026-07-21 03:59Z SFC–400 ft
Atlanta, GA
View FAA NOTAM → - SECURITY6/7597 2026-07-08 16:07Z – 2026-07-21 03:59Z SFC–400 ft
Marietta, GA
View FAA NOTAM → - SECURITY6/7564 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC
View FAA NOTAM → - SECURITY6/3224 2026-07-11 04:01Z – 2026-07-15 03:59Z SFC–1,000 ft
Atlanta, GA, Saturday, July 11, 2026 through Tuesday, July 14, 2026 Local
View FAA NOTAM → - HAZARDS6/4885 2026-07-11 11:00Z – 2026-07-20 01:00Z SFC–5,000 ft
14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/4910 2026-07-11 11:33Z – 2026-07-20 01:00Z SFC–5,000 ft
14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/4909 2026-07-11 12:00Z – 2026-07-16 23:59Z SFC–400 ft
Pell City, AL, Saturday, July 11, 2026 through Thursday, July 16, 2026 Local
View FAA NOTAM → - HAZARDS6/4931 2026-07-11 15:58Z – 2026-07-23 01:00Z SFC–3,000 ft
2NM NE SHALLOTTE, NC, Saturday, July 11, 2026 through Thursday, July 23, 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 36
- 1153 ft AGL at event
- 176 kt ground speed
- 0 fpm vertical
- Approach stability 59/100
- 4 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KHRT 161855Z AUTO 11015G17KT 10SM CLR 33/21 A3019 RMK AO2 SLP221 T03310206 FZRANO $
Flight context
- LOBO148
- C560
- KNKT → KHRT
- 2026-07-13 17:31 UTC
- KHRT runway 36
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