LAX97LA271 · Miller S-1
Miller S-1 · Accident: loss of control on ground/water during landing
From 7E7 · Camp Verde, AZ to P52
Event
- NTSB case
- LAX97LA271
- 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
Miller S-1
- Aircraft type
- Miller S-1
- 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
- N22RM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 7E7 · Camp Verde, AZTo P52
- 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
- Flight control, rudder › Inadequate
- Landing gear, main gear › Inadequate
- Landing gear, normal brake system › Failure
- Landing gear, normal brake system › Inadequate
- Landing gear, tailwheel assembly › Inadequate
- Owner/builder › Acft/equip, inadequate design
- Owner/builder › Maintenance, installation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed the morning of the accident to get the feel of the airplane. He was coming in for his fourth touchdown when he said he came in too fast and rolled out too far. He stated the left brake did not respond. A postaccident examination of the aircraft was conducted by an FAA airworthiness inspector. He reported that the aircraft design had several deficiencies. The rudder was very small and the 2-inch tail wheel horn was short. The wheels and brakes were from a Honda motorcycle, which was originally designed for a 200 pound motorcycle. This aircraft weighs approximately 1,200 pounds. The pilot had 2 hours of flight time in this airplane prior to the accident flight. There were no preimpact failures noted on the wheels and brakes.
Probable cause
The inadequate strength and braking capability of the landing gear and wheel brakes, and the builder's attempt to adapt motorcycle parts to an aircraft application. A factor in this accident was the pilot's lack of familiarity with this experimental aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX97LA271
- Event ID
- 20001208X08667
- Case number
- LAX97LA271
- 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: 2909943238c168e146473dcc3d56e136f14f171c895a3c9da34e0e797ca53807; retrieved 2026-09-22T18:53:20.483Z.