FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA069 · Cirrus Design Corp SF50

3 Jan 2025 · Spearfish, SD, United States

Foxtrot Jet Cirrus Design Corp SF50 · Accident: system/component malfunction/failure (non-power) during landing

From Saint Paul Downtown Holman Field (STP) to Black Hills Airport-Clyde Ice Field (SPF)

Report a problem

Event

NTSB case
CEN25LA069
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cirrus Design Corp SF50

Aircraft type
Cirrus SF50
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N603AP
Operator
Foxtrot Jet
Onboard fatalities
Unknown
Route
From Saint Paul Downtown Holman Field (STP), St. Paul, MNTo Black Hills Airport-Clyde Ice Field (SPF), Spearfish, SD
Aircraft age
About 7 years (built 2018)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On January 3, 2025, about 2338 mountain standard time, a Cirrus Design Corporation SF-50 airplane, N603AP, was substantially damaged when it was involved in an accident near Spearfish, South Dakota. The pilot and five passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot reported the flight proceeded uneventfully until landing. The air traffic controller advised him that the Black Hills Airport-Clyde Ice Field (SPF) runway was covered with 1/8” of wet snow. However, the runway braking action was reported as 5/5/5 (touchdown/midpoint/rollout) meaning that braking action was good and all portions of the runway wet including the presence snow. The airport was in sight about 4 miles out, and the pilot executed a straight-in approach to runway 13. He verified that the landing gear was down. His intention was to touchdown at the landing reference speed (Vref) to minimize the need for braking. He disconnected the autopilot at 2 miles from the runway, and the airplane appeared to be lined up with the extended runway centerline.

The pilot recalled that during landing, about 8 to 10 feet above ground level (agl), he received an aerodynamic stall warning with the stick shaker. At first, the touchdown seemed normal, but then the airplane started drifting to the left. The pilot efforts to maintain directional control were not successful. The airplane “lurched hard” when it impacted the snowbank along the left side of the runway. When the airplane came to rest, he shut down the engine, and the airplane was evacuated.

One of the passengers reported that he was seated behind the right-side (co-pilot) seat and had a “good view” out of the windshield. He confirmed seeing the 3-green landing gear down lights while on approach. He noted that the airplane appeared to be aligned with but was slightly left of the runway centerline. As the airplane touched down, it quickly drifted to the left. The left wing then caught the snowbank, and the airplane departed the left side of the runway. The airplane ultimately came to rest with the nose perpendicular to and facing the runway. The passenger recalled that when he exited the airplane, the wind was almost calm.

A Federal Aviation Administration (FAA) inspector responded to the accident site the following day. He reported that the airplane had been moved to the ramp area of the airport. The right wing had substantial sustained damage which included deformation and delamination of the wing structure, partial separation of the right aileron, and damage to the fuel tank. The left main landing gear was extended, the right main landing gear was retracted in the wheel well, and the nose landing gear was collapsed. When the right landing gear was extended after recovery, the tire was still on the wheel rim and appeared intact, but the tire was flat.

The FAA inspector observed runway wheel marks (compressed snow) that corresponded to the accident airplane. The airplane appeared to have touched down about 150 feet before the 1,000-foot / touchdown zone markers. At touchdown, the left main wheel was 6 to 8 feet from the left side of the runway. The airplane departed the left side of the runway about 140 feet after it touched down. The snowbanks on each side of the runway were 2 to 3-feet high. The airplane struck two runway edge lights during the excursion.

Further examination of the airplane and download of available onboard data is pending.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN25LA069
Event ID
20250106199508
Case number
CEN25LA069
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2025-01-04.
  • API snapshot SHA-256: 84c48d80f2a23df5b3610e74d61f2f3c59c0bee1361a4954ec4902e52187a3a8; retrieved 2026-09-16T19:34:55.677Z.