NYC04LA140 · Aviat Pitts S2B
Aviat Pitts S2B · Accident: airframe, component or system failure during landing
From Butler Co Regional Airport - Hogan Field (HAO) to an unrecorded destination
Event
- NTSB case
- NYC04LA140
- 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
Aviat Pitts S2B
- Aircraft type
- Aviat PITTS S2B
- 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
- N963CB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Butler Co Regional Airport - Hogan Field (HAO), Hamilton, OHTo 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
- Landing · landing roll
- 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 › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After completing a 1-hour flight, which included sustained inverted flight, the pilot returned to land. The pilot stated that after touching down on runway 29, a 5,500-foot long, 100-foot wide asphalt runway, the right landing gear brake stuck. The airplane veered to the left, departed the runway surface, and struck a taxiway sign with the right wing. The right landing gear assembly collapsed, and the airplane came to rest in a grass area. Examination of the brake system by a Federal Aviation Administration inspector did not reveal any abnormalities. The winds recorded at the airport, about the time of the accident, were from 230 degrees 12 knots, gusting to 18 knots.
Probable cause
The pilot's failure to maintain directional control after experiencing a brake system malfunction during landing. Factors related to the accident were the malfunction of a landing gear brake as reported by the pilot, and the crosswind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC04LA140
- Event ID
- 20040630X00885
- Case number
- NYC04LA140
- 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: 6d59c2eb20ffec8b702d7d847f1b8ed2bc7264e584733579b98c044ef46e0352; retrieved 2026-09-22T07:20:29.350Z.