WPR12FA349 · Cessna P210N
Cessna P210N · Accident during an emergency descent
From Santa Monica Municipal Airport (SMO) to Santa Monica Municipal Airport (SMO)
Event
- NTSB case
- WPR12FA349
- 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
- 1 · 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
Cessna P210N
- Aircraft type
- Cessna 210
- 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
- N41KA
- Operator
- Mcmillan M Sean · private individual
- Onboard fatalities
- Unknown
- Route
- From Santa Monica Municipal Airport (SMO), Santa Monica, CATo Santa Monica Municipal Airport (SMO), Santa Monica, CA
- 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
- Emergency descent
- 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
- Unknown or undetermined
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Aircraft › Aircraft oper/perf/capability
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
About 15 minutes after departure, the pilot contacted air traffic control and requested a return to the departure airport without indicating the reason. About 10 minutes later, the pilot was instructed to enter a right base leg for the runway and was subsequently cleared to land behind traffic. One minute later, the pilot declared an emergency, but he did not identify the nature of the emergency. No further transmissions were made by the pilot. The airplane then collided with treetops on a southeasterly heading about 3 miles northeast of the airport and continued about 200 feet before striking the top of a palm tree and falling to the ground. A postcrash fire consumed the majority of the airplane.
Postaccident examination of the airframe revealed no mechanical anomalies that would have precluded normal operation. The engine spark plugs were covered in heavy, dark soot indicative of an extremely rich mixture condition, which could have resulted in a loss of engine power. The engine was examined and subsequently placed on a test stand. After repairs were made to facilitate an engine run, the engine started, ran, and responded to throttle movements with no discrepancies noted. The reason for the return to the departure airport and subsequent reported emergency could not be determined.
The investigation found that the pilot may have had therapeutic levels of doxylamine, a sedating antihistamine, in his blood about the time of the accident. However, based on the circumstances of the accident, it is unlikely that pilot impairment from doxylamine contributed to the accident. Further, the carbon monoxide present in the pilot's blood is consistent with postaccident exposure to combustion products.
Probable cause
The pilot's failure to maintain altitude during a return to the airport following an unspecified emergency; the nature of the emergency could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12FA349
- Event ID
- 20120811X63955
- Case number
- WPR12FA349
- 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 2012-08-11.
- API snapshot SHA-256: 87d720a060a572d736314db22c71128b02a921eab7e93b95bf3ec0afe81f5875; retrieved 2026-09-13T22:33:10.062Z.