Unstable approach — N665KB

N665KB (Mastercorp Aviation) was operating from KORL to KCSV on 2026-07-02. SkyMeter detected a low approach-stability score at Crossville Memorial Whitson Field (KCSV) on runway 26 at 23:05 UTC. Trace data at the event: 2898 ft AGL, 171 kt GS. Approach stability score: 57/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 8 kt wind, 2 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.

• SECURITY6/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• SECURITY6/3991 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/8212 2026-06-17 04:01Z – 2026-07-17 03:59Z SFC–400 ft

  Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 2026 Local

  View FAA NOTAM →
• SECURITY6/0854 2026-06-29 12:30Z – 2026-07-03 06:00Z SFC–2,500 ft

  MAYPORT, FL, Monday, June 29, 2026 through Friday, July 3, 2026 Local

  View FAA NOTAM →
• SECURITY6/1077 2026-07-02 05:00Z – 2026-07-03 09:30Z SFC–17,999 ft

  Macon, GA, Thursday, July 2, 2026 through Friday, July 3, 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.

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