BFO89DID01 · Halstead SANDPIPER
Halstead SANDPIPER · Accident: loss of control in flight on approach
Event
- NTSB case
- BFO89DID01
- 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
Halstead SANDPIPER
- Aircraft type
- Halstead SANDPIPER
- 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
- N339RH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Approach · VFR go-around
- 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 in flight
- 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
- Tree(s)
- 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
- Flight control, ruddervator › Movement restricted
- Pilot in command › Maintenance, installation, improper
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACCIDENT OCCURRED ON THE MAIDEN TEST FLIGHT OF THE RECENTLY CERTIFICATED HOMEBUILT ACFT. THE PLT/BUILDER REPORTED NO PROBLEMS DURING HIGH SPEED TAXI RUNS. AFTER TAKEOFF THE PLT ENCOUNTERED PROBLEMS AT SLOW SPEEDS WHICH DECREASED AS AIRSPEED INCREASED. DURING LANDING, THE ACFT STALLED HIGH AND BOUNCED TWICE ON THE RWY. THE PLT INITIATED A GO-AROUND AND DURING CLIMB OUT WAS UNABLE TO DECREASE PITCH TO GAIN AIRSPEED. THE ACFT CRASHED INTO TREES NEAR THE RWY. THE PLT DESIGNED AND BUILT THE ACFT WITH THE EXCEPTION OF THE DAVIS MIXING UNIT WHICH CONTROLS PITCH AND RUDDER INPUT TO THE RUDDERVADOR. THE DESIGN PLANS CALLED FOR 9 DEGS PITCH UP TRAVEL AND 8 DEGS PITCH DOWN TRAVEL. INVESTIGATION REVEALED THE RUDDERVADOR HAD BEEN INSTALLED WITH 12.5 DEGS NOSE UP TRAVEL AND 4.5 DEGS NOSE DOWN TRAVEL, THUS LIMITING THE PLTS ABILITY TO LOWER THE NOSE DURING CLIMB.
Probable cause
THE PILOT/BUILDERS IMPROPER INSTALLATION OF THE RUDDERVADOR AND THE PILOT'S IMPROPER RECOVERY FROM A BOUNCED LANDING. A CONTRIBUTING FACTOR WAS THE FAILURE OF THE FAA TO DETECT THE FLAW DURING THE CERTIFICATION OF THE AIRCRAFT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO89DID01
- Event ID
- 20001213X27846
- Case number
- BFO89DID01
- 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: 1368fceabbed5675c26883202c0d3da73873443431d1bdb1ebf1454984ece1a5; retrieved 2026-09-23T07:47:53.852Z.