FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA04LA196 · Dornier DO27A4

8 May 2004 · Marion, MT, United States

Dornier DO27A4 · Accident: hard landing

From Ferndale Airfield (53U) to Cabin Creek Landing Airport (97MT)

Report a problem

Event

NTSB case
SEA04LA196
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

Dornier DO27A4

Aircraft type
Dornier DO27
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
N276MK
Operator
Joan M. Colby · private individual
Onboard fatalities
Unknown
Route
From Ferndale Airfield (53U), Ferndale, MTTo Cabin Creek Landing Airport (97MT), Marion, MT
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 · flare/touchdown
First occurrenceThe 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
Hard landing
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

  • Pilot in command › Flare, improper

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

NTSB narrative

Approaching the destination airfield, the pilot reported rain showers were present and the weather was deteriorating. The pilot elected to use the slip maneuver on her landing approach, taking out 90 percent of the slip prior to the airplane touching down hard on its left main landing gear. Witnesses attending the fly-in reported that the left main landing gear was bent and the left door wouldn't operate properly. Later in the afternoon the pilot asked several other pilots their opinions on the left landing gear, and 5 or 6 pilots said it was solid. After securing the left door with rope, the pilot then flew the airplane to her home base. Substantial damage to the airplane was discovered two months after the accident as the aircraft was being repaired. The accident was reported to the FAA on November 4, 2004.

Probable cause

The pilot's improper landing flare resulting in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA04LA196
Event ID
20050207X00144
Case number
SEA04LA196
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 99222c804701530c9bbf1e0cc0635c22ed074ee9c6f9ecee71d5810a3f0aea42; retrieved 2026-09-22T07:35:57.610Z.