LAX99GA005 · Grumman TS-2A
Grumman TS-2A · Accident: in flight collision with terrain/water while maneuvering
From Hemet Ryan Airport (HMT) to Hemet Ryan Airport (HMT)
Narrative check · The NTSB narrative appears to contradict this record's operation. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX99GA005
- 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 Possible conflict
- 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
Grumman TS-2A
- Aircraft type
- Grumman TS-2
- 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
- N416DF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hemet Ryan Airport (HMT), Hemet, CATo Hemet Ryan Airport (HMT), HEMET-RYAN, CA
- 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 · aerial application
- 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
- In flight collision with terrain/water
- 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
- Pilot in command › Low altitude flight/maneuver, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The air tanker pilot was on a fire suppression mission with fire retardant chemicals aboard, and had made two previous drops on the fire line. Another tanker and spotter pilot witnessed the last drop approach, and reported that the pilot was turning from base leg to the westerly drop heading downwind while in a 60-degree left bank. The aircraft suddenly rolled left to 90 degrees, and at that point the left wing tip struck the terrain. The winds were estimated by the tanker pilots to be 25 to 30 mph with gusts to 40 plus from the east. The pilots also reported turbulence and bad air. Airmet Tango was issued for turbulence and isolated severe conditions mainly below 10,000 in the vicinity of canyons and passes.
Probable cause
The pilot misjudged his maneuvering altitude. Factors to this accident were the mountainous terrain, tailwind conditions, and turbulence in the area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99GA005
- Event ID
- 20001211X11282
- Case number
- LAX99GA005
- 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: b5fca3d45e52ebf34c04d2165ba47de09bff9fac1fdf8944c1b101f94350628d; retrieved 2026-09-20T22:22:18.692Z.