CEN13CA007 · Cirrus Design Corp SR20
Hummingbird Ventures Cirrus Design Corp SR20 · Accident: landing area overshoot
From Airlake Airport (KLVN) to Flying Cloud Airport (KFCM)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN13CA007
- 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
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- 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 SR20
- Aircraft type
- Cirrus SR20
- 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
- N750SR
- Operator
- Hummingbird Ventures
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Airlake Airport (KLVN), Airlake, MNTo Flying Cloud Airport (KFCM), Flying Cloud, MN
- Aircraft age
- Not recorded
- 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
- Landing area overshoot
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he flew a visual approach and landed near the midpoint of a 2,691-foot-long runway. The wind was at 5 knots and aligned with the runway, which was dry. After landing, the pilot applied “light/normal braking” but noticed his deceleration rate was inadequate to stop on the remaining runway. The pilot subsequently applied heavier braking, but the brakes “seemed to have no effect.” Realizing he was not going to stop the airplane on the remaining runway, the pilot attempted a go-around near the departure end of the runway. The airplane never became airborne, departed the runway, and impacted an airport perimeter fence. Substantial damage to the airplane included impact damage to both wings and ailerons. Skid marks from the accident airplane were documented near the departure end of the runway. A postaccident examination of the braking system of the airplane revealed no mechanical malfunctions that would have precluded normal operation.
Probable cause
The pilot’s inadequate braking action and decision to abort the landing near the departure end of the runway. Contributing to the accident was the pilot’s attempt to land near the midpoint of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13CA007
- Event ID
- 20121007X75550
- Case number
- CEN13CA007
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 55f6b49dc61f2e79b5afcdc9d1573fc7fec395eccd40b18f2b86132560b61d2b; retrieved 2026-09-15T20:07:07.512Z.