The U.S. aircraft register, updated daily
Accidents · NTSB FTW98FA156 · Final report

Bell 206-A accident near Rio Hondo, Texas, March 24, 1998

On March 24, 1998 at about 7:30 pm local time, a Bell 206-A (helicopter), registered TGJET, was destroyed in an accident near Rio Hondo, Texas. It was a ferry flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The engine compartment fire due to undetermined reasons, which resulted in the in-flight separation of the tailboom.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 24, 1998 · about 7:30 pm local time
Place
Rio Hondo, Texas · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Bell 206-A · all 206-As on the register
Registration
TGJET · no longer on the register · serial 86
Damage
Destroyed
Flight
Ferry flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

A witness observed the Bell 206-A helicopter 'flying fast' in a southerly direction at about 500 to 600 feet agl. Flames were coming from the helicopter's right rear side in the vicinity of the engine compartment, and very little smoke was observed. Prior to descending from view, the helicopter appeared to be in controlled flight. Subsequently, the aircraft impacted the ground and was destroyed by the in-flight and postimpact fire. Examination of the engine compartment revealed that the step portion of the forward firewall where the throttle and fuel line pass through had localized bluing; however the fuel line connector which was still attached to the firewall fitting, did not exhibit any fire damage. The #3 tail rotor drive shaft segment was found 66 feet prior to the initial impact scar. It was fractured with fire damaged fiberglass cloth wrapped around the forward end of the fractured shaft. According to a NTSB metallurgist, 'the fracture was consistent with an overstress after exposure to elevated temperatures.' The helicopter was returning to Guatemala after completion of schedule maintenance performed in the United States.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: rotorcraft: helicopter
  • Flight time: 310 hours in all
  • Medical certificate: Class 2 (valid medical--no waivers/lim.)
  • Seat: rgt

The aircraft

  • Airframe total time: 2,457 hours
  • Last inspection: annual inspection, March 23, 1998; 5 hours since
  • Maximum gross weight: 3,000 lb
  • Seats: 5
  • Landing gear: fixed
  • Engine: Allison 250-C18 (turboshaft); 0 hours total

The flight

  • Departed from: 3R5 New Braunfels TX at 5:00 pm
  • Destination: BRO Brownsville TX
  • Flight plan: none
  • Runway 0

Weather at the time

  • Light: daylight
  • Wind: from 160° at 35 knots
  • Sky: clear
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.