FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04LA253 · Anderson Harmon Rocket II

7 Jul 2004 · Seal Beach, CA, United States

Anderson Harmon Rocket II · Accident: airframe, component or system failure en route

From Zamperini Field (TOA) to Chino Airport (CNO)

Report a problem

Event

NTSB case
LAX04LA253
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
1 · 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
Instrument Meteorological Cond

Anderson Harmon Rocket II

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
N28BE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Zamperini Field (TOA), Torrance, CATo Chino Airport (CNO), Chino, CA
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
En route · cruise
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
Destroyed

Cause areas

  • Flight control, elevator › Separation
  • Flight control, rudder › Separation
  • Pilot in command › Aircraft control, not possible

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane collided with a residence following an in-flight separation of the vertical stabilizer, elevator, and upper rudder, which resulted in an uncontrolled descent. The pilot, who was also the builder of the airplane, was on an instrument flight. While established in cruise flight at an elevation of approximately 5,000 feet mean sea level and 200 knots, radar contact was suddenly lost when the airplane entered a rapid descent. Review of the aircraft's radar data revealed primary radar returns were located near the aircraft's mode C returns near the time of the upset. Aerial and ground searches using trajectory data analysis on the primary radar returns commenced; however, no additional components were located. During a post-accident examination of the wreckage, investigators were unable to identify the stabilizer. The day prior to the accident the pilot indicated that he was experiencing control problems with the elevator trim system on the airplane. A manufacturer of another experimental aircraft kit, similar in design to the accident airplane kit, performed structural testing of his kit. These tests indicated that the flight loading could exceed the structural strength of the horizontal and vertical stabilizer control surface so modifications were made in his model to increase the structural strength. These structural modifications were not completed in the accident airplane, nor were they required. There is no requirement for experimental aircraft manufacturers or kit suppliers to analyze the structural integrity of the airplane throughout its operating envelope, nor does a builder have to establish the adequacy of the design during flight tests. The pilot's immediate family had a history of sudden death due to aneurisms and heart failure. Due to the circumstances of the accident, no usable medical data could be obtained to discern the pilot's medical condition at the time of the accident.

Probable cause

the in-flight separation of the elevator, which resulted in a loss of airplane control and an uncontrolled descent. The underlying cause and mechanism of the elevator separation could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04LA253
Event ID
20040713X00959
Case number
LAX04LA253
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: 0846eac5ba6d37da22d48954d9824f3de38a216cf72fe9c5b3c510f944064ced; retrieved 2026-09-20T18:25:30.395Z.