LAX97LA132 · Beech 100
A&a Reomix Concrete Mix Beech 100 · Accident: hard landing
From San Carlos Airport (SQL) to an unrecorded destination
Event
- NTSB case
- LAX97LA132
- 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 100
- Aircraft type
- Beechcraft 100
- 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
- N60TJ
- Operator
- A&a Reomix Concrete Mix
- Onboard fatalities
- Unknown
- Route
- From San Carlos Airport (SQL)To not recorded
- 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
- 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
- Pilot in command › Maintenance, adjustment, improper
- Pilot in command › Operation with known deficiencies in equipment, attempted
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the aircraft operator, during a landing, the aircraft dropped approximately 10 feet onto the runway. The aircraft touched down with enough force as to warrant concern by the operator and the pilot. The pilot stated that the gear warning horn was activated after the landing. He examined the landing gear and bent the squat switches to silence the horn, then conducted a test flight. Before landing, three green gear down lights were observed; however, the left landing gear collapsed during the rollout. Before coming to rest, the aircraft struck a sign and three runway lights. The aircraft landing gear was inspected by the FAA and a technical representative (tech rep) from Raytheon Aircraft Company. The tech rep reported that the downlock plates were bent from the hard landing. Review of the logbooks revealed that the aircraft did not have a primary 150-hour inspection, since August 1993, and was in an unairworthy condition. Due to the extent of damage to the landing gear, no preexisting anomalies in those components could be identified.
Probable cause
the pilot's improper flare, which resulted in a hard landing; his improper adjustment of the landing gear warning horn squat switch(es); and his decision to attempt flight with known equipment deficiencies.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX97LA132
- Event ID
- 20001208X07584
- Case number
- LAX97LA132
- 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: 19734a0d3375bff4ed3733afbaddf7eb98f87df71c1f19e763282fb3fb91e58b; retrieved 2026-09-22T20:07:37.079Z.