Unstable approach — EJM736
KHLR · 16H2026-08-18 02:54 UTC· KOPF → KHLR· MILAM AVIATION LLC· CL60
EJM736 (Milam Aviation) was operating from KOPF to KHLR on 2026-08-18. SkyMeter detected a low approach-stability score at Hood Army Air Field (KHLR) on runway 16H at 02:54 UTC. Trace data at the event: 2014 ft AGL, 158 kt GS. Approach stability score: 44/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 7 kt wind, 3 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)- SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft
South Padre Island, TX, Tuesday, May 6, 2025 Local
View FAA NOTAM → - SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - HAZARDS6/2568 2026-08-06 14:22Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2575 2026-08-06 15:06Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2751 2026-08-07 00:16Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Friday, August 7, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3249 2026-08-10 15:17Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Monday, August 10, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3405 2026-08-10 16:03Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Monday, August 10, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - SECURITY6/5452 2026-08-17 12:30Z – 2026-08-22 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, August 17, 2026 through Saturday, August 22, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/4820 2026-08-18 00:21Z – 2026-08-18 01:49Z SFC–180 ft
Cape Canaveral, FL, Monday, August 17, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/4822 2026-08-18 00:21Z – 2026-08-18 01:49Z SFC–180 ft
Cape Canaveral, FL, Monday, August 17, 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 16H
- 2014 ft AGL at event
- 158 kt ground speed
- 0 fpm vertical
- Approach stability 44/100
- 7 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KHLR 100455Z AUTO 15008KT 10SM CLR 28/21 A3004 RMK AO2 SLP160 T02780213
Flight context
- EJM736
- Milam Aviation
- CL60
- KOPF → KHLR
- 2026-08-18 02:54 UTC
- KHLR runway 16H
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