LAX04CA122 · McDonnell Douglas 369FF
McDonnell Douglas 369FF · Accident: hard landing
From Falcon Field (FFZ) to Falcon Field (FFZ)
Event
- NTSB case
- LAX04CA122
- 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
McDonnell Douglas 369FF
- Aircraft type
- McDonnell Douglas 369
- Category
- Helicopter
- 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
- N630N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Falcon Field (FFZ), Mesa, AZTo Falcon Field (FFZ), Mesa, AZ
- 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 · flare/touchdown
- 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
- Hard landing
- 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(cfi) › 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
The helicopter's main rotor blades struck the tail boom following a hard landing. The pilot was demonstrating full-touchdown, practice autorotations for a potential customer. Before touching down, about 2 feet above ground level, the helicopter encountered a gust of wind and the nose turned 45 degrees to the left. The pilot applied right pedal pressure to counteract the sudden drift, but was unable to get the helicopter back on centerline. During touchdown, the helicopter landed hard and skidded about 4 feet until it came to rest without incident. A few seconds later, the pilot heard a loud noise. The main rotor blades had collided with the tail boom. The pilot did not report any mechanical problems with the helicopter prior to the accident.
Probable cause
the pilot's inadequate compensation for the wind gusts and subsequent failure to maintain directional control of the helicopter, which resulted in a hard landing. A contributing factor was a wind gust.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04CA122
- Event ID
- 20040306X00284
- Case number
- LAX04CA122
- 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: 65d5800fbce664a375c228502d9ae02fcb15f87e6f939d39e5109b619eebe475; retrieved 2026-09-22T07:58:20.872Z.