LAX99FA311 · No American/Rogers B L P-51R
No American/Rogers B L P-51R · Accident: airframe, component or system failure while maneuvering
From 4SD to an unrecorded destination
Event
- NTSB case
- LAX99FA311
- 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
- 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
No American/Rogers B L P-51R
- Aircraft type
- No American/rogers P-51
- 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
- N57LR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 4SDTo 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
- Maneuvering
- 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
- Empennage › Separation
- Flight control, rudder › Flutter
- Flight control, rudder › Separation
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The empennage assembly of the experimental race plane separated and the aircraft crashed during the first lap of an unlimited class heat race at the Reno National Championship Air Races. The wreckage was spread over approximately a 0.5-mile path. The first item located in the wreckage path was the lower half-span of the rudder control. Approximately 1/8 mile further along the debris path was a wreckage field about 500 feet long containing the remainder of the empennage (including the rudder trim tab), except the rudder upper half-span. The rudder upper half-span, including the mass balance, was located about 1,900 feet to the right of the debris field. When laid together, the rudder exhibited a shredded appearance through the midspan forward of the rudder trim tab location. Review of a spectator video recording taken from the rear in the seconds before the accident showed that, while the other parts of the aircraft were visible, the rudder and vertical stabilizer were not visible. The video technician opined that the disappearance of the vertical fin and rudder might have been the result of 'video smearing' if the rudder was moving rapidly and the video image recorder rate could not keep up with it. The precipitating event was not determined during extensive reconstruction and analysis of the empennage.
Probable cause
The onset of a flutter event and the resultant separation of the rudder and empennage from the aircraft. The precipitating cause for the flutter could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99FA311
- Event ID
- 20001212X19791
- Case number
- LAX99FA311
- 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: 528ba40882dbb854c7956e3b59db2f99e29da4237c81974ade81cb619ddd9531; retrieved 2026-09-20T21:47:46.993Z.