MIA05LA086 · Frank D. Amador Searey
Frank D. Amador Searey · Accident: airframe, component or system failure during takeoff
From Haller Airpark (7FL4) to an unrecorded destination
Event
- NTSB case
- MIA05LA086
- 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
- Unknown
- 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
Frank D. Amador Searey
- Aircraft type
- Frank D Amador SEAREY
- 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
- N43427
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Haller Airpark (7FL4), Green Coast Spr, FLTo 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
- Takeoff · roll/run
- 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
- Airframe, component or system failure
- 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
- Owner/builder › Maintenance, installation, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that as he slowly added power to take off, and as the speed increased, it required more right rudder control input to bring the airplane back to the centerline of the runway. At about 45 mph he said he aborted the takeoff, far to the left of the centerline, and the airplane departed the runway and ultimately impacted a tree. According to an FAA inspector who responded to the accident, the airplane's rudder had jammed full to the left, and the pilot's left rudder control cable was found to have jammed between the upper seat rail structure tube, and the lower rudder foot rest rail structure tube. After the cable was released, full rudder travel was restored in both directions. The inspector further stated that when he examined how the rudder cables had been routed, it appeared to him that the rudder cable on the right side of the airplane had been routed with greater separation between it and the rails, when compared with the left cable, which had jammed.
Probable cause
The airplane builder's improper installation of the left rudder control cable, which resulted in the cable becoming jammed, a loss of directional control during takeoff, and the airplane departing the runway and impacting a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA05LA086
- Event ID
- 20050420X00486
- Case number
- MIA05LA086
- 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, coordinates. 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: 6030bc500bcccd6cfc925fb632b4eb8601867a01a8b6f03e06248c34f509bffc; retrieved 2026-09-21T09:08:58.629Z.