SEA00TA138 · Cessna 182R
Civil Air Patrol (oregon Wing) Cessna 182R · Accident: hard landing
From Roberts Field (RDM) to 5J0
Event
- NTSB case
- SEA00TA138
- 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
- 0
- 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
- Government
- 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
Cessna 182R
- Aircraft type
- Cessna 182
- 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
- N101SP
- Operator
- Civil Air Patrol (oregon Wing)
- Onboard fatalities
- Unknown
- Route
- From Roberts Field (RDM), Redmond, ORTo 5J0
- 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
- Public Aircraft
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The Cessna 182R pilot reported that he set up for a straight-in visual approach to runway 09. About 2 miles out he lowered 10 degrees flaps and established 80 knots airspeed. About 1 mile out he lowered the flaps to 20 degrees maintaining 80 knots, and about 1/2 mile out he lowered the flaps to 30 degrees, established his speed between 70-80 knots, and then began the flare. Upon touchdown of the nose wheel, a loud 'chattering' noise ensued along with an intense vibration. The aircraft's nose wheel bounced twice on the pavement with the propeller making runway contact after the third bounce. A 'zigzag' black scuff mark on the runway pavement slightly left of the centerline was observed, along with two gouges in the asphalt roughly perpendicular to the track of the scuff. Post-crash examination of the damaged nose wheel fracture surfaces revealed evidence typical of overstress separation. All the bearing components were covered with an abundant amount of a lubricant and exhibited no heat tinting. No evidence of fatigue cracking was found in the fracture faces.
Probable cause
The pilot's improper flare on touchdown resulting in a hard landing. A factor was the pilot's entrance into an inadvertent porpoise condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA00TA138
- Event ID
- 20001212X21623
- Case number
- SEA00TA138
- 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. 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: 5d08c8b2d0d611d939b415cfa1c01907f7917d2d75792e74b01e58ccb08d1c67; retrieved 2026-09-18T21:21:03.646Z.