FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW99LA255 · Bell OH-58A

26 Sept 1999 · RATCLIFF, TX, United States

Bell OH-58A · Accident: in flight collision with object while maneuvering

From Jasper, TX (no airport) to an unrecorded destination

Report a problem

Event

NTSB case
FTW99LA255
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
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
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 OH-58A

Aircraft type
Bell OH-58
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
N523SP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jasper, TX (no airport)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 137: Agricultural
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 object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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 › Clearance, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The helicopter contacted a tree during an aerial application flight. According to the pilot he was turning from the south toward the east when he became distracted due to the 'sun, and making an input into the GPS receiver.' Subsequently, the tailrotor blades contacted a tree, the helicopter impacted the ground, and the tailboom separated.

Probable cause

The pilot's failure to maintain clearance with the tree while maneuvering during an aerial application flight. Factors were the sunglare, and the pilot's diverted attention while adjusting the GPS receiver.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW99LA255
Event ID
20001212X19765
Case number
FTW99LA255
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: bd043ec53f74eebfaff422e46a0beb6b0e62d7aa911069768f63e5b9f2a8a1c8; retrieved 2026-09-22T14:00:10.460Z.