FTW99LA048 · Aerospatiale AS-350-BA
Aerospatiale AS-350-BA · Accident: roll over during takeoff
From San Angelo Regional Mathis Field (SJT) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- FTW99LA048
- 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
Aerospatiale AS-350-BA Possible conflict
- Aircraft type
- Aerospatiale AS-350
- 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
- N911MV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From San Angelo Regional Mathis Field (SJT)To 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
- Takeoff
- 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
- Roll over
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The instructor pilot-command (PIC) of the twin-engine helicopter was giving a newly hired pilot a check out and instruction. After completion of a practice 'hydraulic system off' landing, the PIC performed a normal takeoff (with hydraulics 'ON'). During the takeoff, the helicopter rolled over to the left, and the main rotor blades impacted the ground. The PIC reported that it felt like a 'hydraulic hardover.' Examination of the hydraulic system after the accident did not reveal any defects or anomalies that would validate a hydraulic hardover.
Probable cause
the rollover during take off for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW99LA048
- Event ID
- 20001211X11561
- Case number
- FTW99LA048
- 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: 09c925d9a0999d60e0a58dcb0f113f8362dc1c2cfef1797c8e0a423f6be614a8; retrieved 2026-09-22T16:09:38.858Z.