Go-around — WOLF01
KBIL · 28R2026-06-05 15:18 UTC· KOKC → KBIL· UNITED STATES NAVY· B738
WOLF01 (United States Navy) was operating from KOKC to KBIL on 2026-06-05. SkyMeter detected a go-around at Billings Logan International Airport (KBIL) on runway 28R at 15:18 UTC. Trace data at the event: 3677 ft AGL, 176 kt GS. METAR at the time reported 6 kt wind, 5 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/3585 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft
74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/3649 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft
74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 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 28R
- 3677 ft AGL at event
- 176 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KBIL 181753Z 21007KT 10SM FEW060 FEW110 23/09 A3009 RMK AO2 SLP164 TCU DSNT N T02330094 10233 20117 58004
Flight context
- WOLF01
- United States Navy
- B738
- KOKC → KBIL
- 2026-06-05 15:18 UTC
- KBIL runway 28R
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