Go-around — RCH466

LBSF · 27

2026-02-18 12:53 UTC· KMCF → LBSF· K35R

▶ Replay 📊 Analyse

RCH466 was operating from KMCF to LBSF on 2026-02-18. SkyMeter detected a go-around at Sofia Airport (LBSF) on runway 27 at 12:53 UTC. Trace data at the event: 2150 ft AGL, 176 kt GS. METAR at the time reported 13 kt wind, 7 kt crosswind component, 9,999 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)
  • SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

    NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 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 27
  • 2150 ft AGL at event
  • 176 kt ground speed
  • 0 fpm vertical
  • 13 kt wind
  • 7 kt crosswind component
  • 9,999 m visibility
  • METAR LBSF 231330Z 32014KT 9999 SCT055 BKN071 16/02 Q1021 NOSIG

Flight context

  • RCH466
  • K35R
  • KMCF → LBSF
  • 2026-02-18 12:53 UTC
  • LBSF runway 27

All events on this flight

Go-around 12:53:07 UTC · LBSF runway 27 · 2,150 ft AGL · 176 kt GS
Go-around 12:53:07 UTC · LBSF runway 27 · 2,150 ft AGL · 176 kt GS
Go-around 12:53:07 UTC · LBSF runway 27 · 2,150 ft AGL · 176 kt GS
Go-around 12:53:07 UTC · LBSF runway 27 · 2,150 ft AGL · 176 kt GS

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

SkyMeter · trace data observed via ADS-B· LBSF