Return to field — N412MH
KBOI · 28L2026-08-24 19:24 UTC· KBOI → KBOI· MFH AVIATION LLC· PC24
N412MH (MFH Aviation) had departed KBOI on 2026-08-24. SkyMeter detected a return to field at Boise Air Terminal/Gowen Field (KBOI) on runway 28L at 19:24 UTC. Peak altitude 14,151 ft, turnaround area near Gem, US. Approach stability score: 39/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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/4363 2026-08-12 17:00Z – 2026-08-26 04:00Z SFC–12,500 ft
33NM N BOISE, ID, Wednesday, August 12, 2026 through Wednesday, August 26, 2026 UTC
View FAA NOTAM → - HAZARDS6/4727 2026-08-13 14:00Z – 2026-08-27 04:00Z SFC–12,500 ft
33NM N BOISE, ID, Thursday, August 13, 2026 through Thursday, August 27, 2026 UTC
View FAA NOTAM → - HAZARDS6/5073 2026-08-14 14:00Z – 2026-08-28 04:00Z SFC–12,500 ft
33NM N BOISE, ID, Friday, August 14, 2026 through Friday, August 28, 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 28L
- 14151 ft AGL at event
- 362 kt ground speed
- 0 fpm vertical
- Approach stability 39/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KBOI 162153Z AUTO 34007KT 10SM CLR 27/02 A2996 RMK AO2 SLP123 T02670022
Flight context
- N412MH
- MFH Aviation
- PC24
- KBOI → KBOI
- 2026-08-24 19:24 UTC
- KBOI runway 28L
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