Unstable approach — N711WH

N711WH (KCM Ventures Whitefish 2) was operating from KSNS to K50F on 2026-08-19. SkyMeter detected a low approach-stability score at Bourland Field (K50F) on runway 17 at 01:14 UTC. Trace data at the event: 1968 ft AGL, 163 kt GS. METAR at the time reported 11 kt wind, 2 kt crosswind component. 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.

• SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

  SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/2652 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/4812 2026-07-15 07:00Z – 2027-07-14 06:59Z SFC–17,999 ft

  El Centro, CA, Wednesday, July 15, 2026 through Tuesday, July 13, 2027 Local

  View FAA NOTAM →
• HAZARDS6/2489 2026-08-06 02:15Z – 2026-08-19 04:00Z SFC–9,000 ft

  27NM S BAKERSFIELD, CA, Thursday, August 6, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2435 2026-08-06 13:00Z – 2026-08-20 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2842 2026-08-07 14:30Z – 2026-08-21 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Friday, August 7, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3075 2026-08-08 19:30Z – 2026-08-22 04:00Z SFC–12,000 ft

  28NM NE LAS VEGAS, NM, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3157 2026-08-10 01:18Z – 2026-08-23 15:00Z SFC–7,500 ft

  8NM SE BIG SUR, CA, Monday, August 10, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3480 2026-08-10 18:36Z – 2026-08-23 15:00Z SFC–7,500 ft

  8NM SE BIG SUR, CA, Monday, August 10, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3712 2026-08-11 14:00Z – 2026-08-25 04:00Z SFC–8,000 ft

  18NM SW PRESCOTT, AZ, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4807 2026-08-13 03:30Z – 2026-08-20 03:30Z SFC–8,500 ft

  8NM SE BIG SUR, CA, Thursday, August 13, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4941 2026-08-13 16:00Z – 2026-08-20 03:00Z SFC–11,000 ft

  5NM S BIG BEAR LAKE, CA, Thursday, August 13, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5070 2026-08-14 13:00Z – 2026-08-27 03:00Z SFC–8,500 ft

  8NM SE BIG SUR, CA, Friday, August 14, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5409 2026-08-17 04:00Z – 2026-08-30 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5474 2026-08-17 07:41Z – 2026-08-22 00:15Z SFC–5,000 ft

  IMPERIAL, CA, Monday, August 17, 2026 through Saturday, August 22, 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.

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