FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99LA130 · Beech 58

23 Mar 1999 · Atwater, CA, United States

Beech 58 · Accident: wheels up landing

From Palo Alto Airport (PAO) to Palo Alto Airport (PAO)

Report a problem

Event

NTSB case
LAX99LA130
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 58

Aircraft type
Beechcraft 58
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
N6BY
Operator
Unknown
Onboard fatalities
Unknown
Route
From Palo Alto Airport (PAO), Palo Alto, CATo Palo Alto Airport (PAO)
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
Wheels up 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

  • Dual student › Landing gear, not deployed
  • Pilot in command(cfi) › Supervision, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While in the traffic pattern, the instructor simulated an engine failure and placed an engine in a zero thrust condition. During the approach, the student decided to delay lowering the flaps and gear until turning final. The student said that on final he lowered the flaps to the full down position with both engines near zero thrust. The instructor returned the failed engine on short final. Neither crewmember noticed anything unusual until the aircraft appeared to settle more than expected prior to touchdown. Before either of them could recover, both propellers struck the runway. After the accident, the landing gear system was examined and found to fully function. The damage to the landing gear wheel well doors and the flaps was consistent with both being in transit at the time of ground contact.

Probable cause

the failure of the student to extend the landing gear and the flight instructor's inadequate supervision of the flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99LA130
Event ID
20001205X00351
Case number
LAX99LA130
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: e9eddd66e63ac144dfe44d1a6c208052c297c2d1d5c7509b6b73232e548d9386; retrieved 2026-09-22T15:38:59.511Z.