Long landing rollout — N226SJ
KSDM · 08L2026-06-15 04:26 UTC· SSC ASSET CO II LLC· GLEX
N226SJ (SSC Asset Co II) was inbound to KSDM on 2026-06-15. SkyMeter detected a long landing rollout at Brown Field Municipal Airport (KSDM) on runway 08L at 04:26 UTC. Trace data at the event: 505 ft AGL, 8 kt GS. Approach stability score: 87/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 6 kt wind, 3 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft
Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 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 08L
- 505 ft AGL at event
- 8 kt ground speed
- 0 fpm vertical
- Approach stability 87/100
- 6 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KSDM 182353Z VRB06KT 10SM CLR 23/15 A2999 RMK AO2 SLP149 T02330150 10256 20233 56010 $
Flight context
- N226SJ
- SSC Asset Co II
- GLEX
- 2026-06-15 04:26 UTC
- KSDM runway 08L
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