FTW03TA156 · Bell 407
Bell 407 · Accident: rotor failure/malfunction on approach
From Baton Rouge Metropolitan Airport (BTR) to Franklin
Event
- NTSB case
- FTW03TA156
- 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
- Government
- 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
Bell 407
- Aircraft type
- Bell 407
- 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
- N991SP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LATo Franklin
- 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
- Public Aircraft
- 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
- Approach
- 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
- Rotor failure/malfunction
- 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
- Other maintenance personnel › Maintenance, installation, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
When approaching a helipad for landing, the pilot realized that the anti-torque pedals were not effective. Due to obstacles, the pilot aborted his approach to the helipad and turned eastbound toward a sugar cane field. Subsequently, the helicopter started to rotate and the pilot realized he had no control of the tail rotor with the anti torque pedals. He then rolled the throttle to idle, and initiated an autorotation from approximately 75 feet AGL. The pilot reported that a high sink rate developed and the helicopter impacted the ground hard on the main landing skids. Inspection of the helicopter revealed that the pivot bolt (P/N: NAS6604D31), bushing (P/N: 206-011-726-005), nut (P/N: MS14144l4), and cotter pin (P/N: MS24665-155), that connects the rotor control idler assembly (P/N: 406-012-127-101) to the tail rotor control housing assembly was not found. Examination of the aircraft logbooks indicated that there was an annual maintenance inspection preformed on the helicopter 7 days hours prior to the accident. The helicopter accumulated 4.9 hours of flight time since time of inspection.
Probable cause
The loss of tail rotor effectiveness due to the inadequate maintenance performed by other company personnel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW03TA156
- Event ID
- 20030602X00751
- Case number
- FTW03TA156
- 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: b07836303e496d370880263102376a7784508110baf1b7bcfb2c6d11defe7853; retrieved 2026-09-18T21:17:46.472Z.