FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO90FA053 · Beech 36

2 Jun 1990 · Gaithersburg, MD, United States

Tri-H Beech 36 · Accident: gear not extended during landing

From Richmond International Airport (RIC) to Montgomery County Airpark (GAI)

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
BFO90FA053
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
2 · 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 36

Aircraft type
Beechcraft 36
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
N2003A
Operator
Tri-H
Onboard fatalities
Unknown
Route
From Richmond International Airport (RIC), Richmond, VATo Montgomery County Airpark (GAI), Gaithersburg, MD
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
Gear not extended
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
Stall
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Airspeed, inadequate
  • Pilot in command › Gear extension, not performed
  • Pilot in command › Planning/decision, improper
  • Pilot in command › Stall, inadvertent
  • Pilot in command › Wheels up landing, inadvertent

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

NTSB narrative

WITNESSES NOTICED THE AIRPLANE WAS ON FINAL APPROACH TO RUNWAY 14 WITH THE GEAR UP. SOME OF THE WITNESSES RADIOED THE PILOT TO ALERT HIM OF THE GEAR POSITION, BUT HE DID NOT RESPOND. THE AIRPLANE LANDED GEAR UP, BUT SOON AFTERWARDS, IT BECAME AIRBORNE, CLIMBED ABOUT 30 FEET, AND DESCENDED IN A LEFT BANK. THE AIRPLANE STRUCK THE GROUND EAST OF THE RUNWAY AND CARTWHEELED; IT CAME TO A STOP ON AN ADJACENT TAXIWAY. AN INVESTIGATION REVEALED THERE WERE ABOUT 60 PROPELLER SLASH MARKS ON THE RUNWAY. AN AIRCRAFT EXAMINATION DID NOT DISCLOSE EVIDENCE OF MECHANICAL MALFUNCTION. EXAMINATION OF THE LANDING GEAR ACTUATOR REVEALED IT WAS IN A TRANSIT POSITION, WHICH WAS ABOUT THREE TURNS OF THE MANUAL GEAR HANDLE FROM THE FULL UP (RETRACTED) POSITION OF THE GEAR.

Probable cause

FAILURE OF THE PILOT TO EXTEND THE LANDING GEAR, WHICH RESULTED IN A WHEELS UP LANDING; HIS IMPROPER DECISION TO ATTEMPT A GO AROUND (ABORTED LANDING) AFTER THE AIRPLANE CONTACTED THE RUNWAY; AND HIS FAILURE TO ATTAIN OR MAINTAIN ADEQUATE AIRSPEED WHILE ATTEMPTING TO CLIMB AFTER LIFTOFF.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO90FA053
Event ID
20001212X23333
Case number
BFO90FA053
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: e1530d41b10511f7700cddff3a78439abf4de23c71137461899da7b9f6ce5bfa; retrieved 2026-09-21T02:38:09.249Z.