FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA05LA104 · British Aircraft Corp. (BAC) 167 StrikemasterMK83

15 May 2005 · Boca Raton, FL, United States

British Aircraft Corp. (BAC) 167 StrikemasterMK83 · Accident: airframe, component or system failure during takeoff

From Boca Raton Airport (KBCT) to Florida Keys Marathon International Airport (KMTH)

Report a problem

Event

NTSB case
MIA05LA104
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

British Aircraft Corp. (BAC) 167 StrikemasterMK83

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
N399WH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Boca Raton Airport (KBCT), Boca Raton, FLTo Florida Keys Marathon International Airport (KMTH), Marathon, FL
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

  • Pilot in command › Aborted takeoff, delayed

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 initially stated that he performed a preflight inspection of the aircraft which included a flight control continuity check. He had the passenger disable the gust lock for the flight controls. He performed a flight control continuity check before taxiing onto the runway for takeoff; no discrepancies were reported. The takeoff roll commenced and at the calculated rotation speed (70 knots), he applied back pressure to the stick but noticed an unusual amount of load on the controls. The takeoff roll continued and he performed trim adjustments. He then aborted the takeoff by retarding the throttle, extending the speed brakes, and applying the wheel brakes. He retracted the flaps, briefed the passenger and tower of the situation, and, after realizing that he was unable to stop the airplane on the runway, he opened the canopy. The airplane rolled through a fence then came to rest upright. The pilot also stated that the airplane is kept outside on the ramp at the Boca Raton Airport. Examination of the airplane by an FAA operation's inspector before recovery revealed the control column would only move aft between 1/4 and 1/2 inch. No determination was made as to the position of the control lock in the cockpit. Examination of the airplane following recovery by an FAA airworthiness inspector revealed that the elevator was free to travel through the full range but was noted to be "...very stiff." Additionally, the rudder was "...extremely hard to move in either direction." During movement of the elevator flight control surface, the rudder flight control surface was noted to move, and with movement of the rudder flight control surface, the elevator flight control surface was noted to move. A review of a United Kingdom (U.K.) Civil Aviation Authority (CAA) Mandatory Permit Directive (MPD) No. 2002-001 R1, issued on January 16, 2003, indicates "...partial binding or complete seizure of the elevator/rudder concentric torque tube bearings causing an interconnect between elevator and rudder control systems. This interconnection has resulted in uncommanded rudder movement with the application of elevator control inputs and vice versa. Investigation has determined that bearing seizure was due to inadequate lubrication and water ingress in the elevator torque tube bearings. Aeroplanes subject to external storage are particularly prone to this occurrence." There was no record that U.K. CAA MPD No. 2002-001 R1 had been complied with.

Probable cause

The delay by the pilot-in-command to abort the takeoff after recognizing excessive elevator control forces for undetermined reasons during the landing roll, resulting in the on-ground collision with a fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA05LA104
Event ID
20050518X00627
Case number
MIA05LA104
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: a540170e8e2628b3f52134bde0841ce61e1aaab17c4630827f2785044f9e49bf; retrieved 2026-09-21T19:01:38.690Z.