Unstable approach — N202RL

N202RL (DOC Sugar Master) was operating from KGGG to KL83 on 2026-06-01. SkyMeter detected a low approach-stability score at Thibodaux Municipal Airport (KL83) on runway 26 at 17:04 UTC. Trace data at the event: 1109 ft AGL, 163 kt GS. Approach stability score: 23/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 2 kt wind, 1 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.

• SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

  Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

  View FAA NOTAM →
• SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

  OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft

  Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 2026 Local

  View FAA NOTAM →
• HAZARDS6/3292 2026-05-27 17:20Z – 2026-06-10 00:15Z SFC–2,000 ft

  22NM SW TALLAHASSEE, FL, Wednesday, May 27, 2026 through Wednesday, June 10, 2026 UTC

  View FAA NOTAM →
• SECURITY6/3583 2026-05-28 07:00Z – 2026-06-01 23:00Z

  NEW ORLEANS, LA, Thursday, May 28, 2026 through Monday, June 1, 2026 UTC

  View FAA NOTAM →
• SECURITY6/2647 2026-05-28 12:00Z – 2026-06-02 04:00Z SFC–2,000 ft

  New Orleans, LA, Thursday, May 28, 2026 through Monday, June 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/3335 2026-05-28 12:00Z – 2026-06-02 04:00Z SFC–2,000 ft

  New Orleans, LA, Thursday, May 28, 2026 through Monday, June 1, 2026 Local

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

  BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Miami, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4380 2026-06-01 13:00Z – 2026-06-06 06:00Z SFC–2,500 ft

  MAYPORT, FL, Monday, June 1, 2026 through Saturday, June 6, 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.

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