LAX95LA281 · Beech V35B
Beech V35B · Accident: loss of control on ground/water during landing
From Coeur D'Alene Airport - Pappy Boyington Field (COE) to Minden-Tahoe Airport (MEV)
Event
- NTSB case
- LAX95LA281
- 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
- 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
Beech V35B
- Aircraft type
- Beechcraft 35
- 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
- N444DG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Coeur D'Alene Airport - Pappy Boyington Field (COE), Coeur d'Alene, IDTo Minden-Tahoe Airport (MEV)
- 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 · landing roll
- 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
- Loss of control on ground/water
- 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 › Compensation for wind conditions, improper
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE UNICOM OPERATOR TOLD THE PILOT THAT THE SURFACE WINDS WERE FROM THE WEST AT 20 KNOTS GUSTING TO 35 KNOTS AND SUGGESTED RUNWAY 16. RUNWAYS 30 AND 34 WERE AVAILABLE. THE PILOT LANDED ON RUNWAY 16 AND LOST DIRECTIONAL CONTROL. THE NOSE GEAR COLLAPSED WHEN THE AIRPLANE EXITED THE RUNWAY. THE PILOT SAID THAT HE KNEW HE SHOULD HAVE LANDED ON EITHER RUNWAY 30 OR 34.
Probable cause
The pilot's selection of the wrong runway, improper decision to land with a quartering tail wind, and his improper compensation of the prevailing wind conditions. The gusting crosswind and tail wind were factors in this accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX95LA281
- Event ID
- 20001207X04279
- Case number
- LAX95LA281
- 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: 641bf550f2dc9a5b1532cd77368d4eb299c5939bb254425a67a8544a22d1992b; retrieved 2026-09-22T23:30:21.263Z.