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

Amateur-built 162F accident near Tucson, Arizona, October 19, 2002

On October 19, 2002 at about 6:50 pm local time, a amateur-built 162F (helicopter), registered N162AZ, was destroyed in an accident near Tucson, Arizona (Ryan Field Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

the failure of the secondary drive shaft.

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

What the record shows

Date
October 19, 2002 · about 6:50 pm local time
Place
Tucson, Arizona · Ryan Field Airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built 162F
Registration
N162AZ · no longer on the register · serial 6398
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

Following a drive shaft failure, the helicopter collided with high vegetation and rolled over during an autorotation. In a statement to a Federal Aviation Administration (FAA) inspector, the pilot reported that while performing pattern and ground reference maneuvers, the helicopter experienced a mechanical malfunction. The pilot executed an autorotation and contacted high vegetation with the helicopter's right skid, resulting in the helicopter rolling to the left and impacting terrain. The pilot disposed of the helicopter in a waste dump prior to examination by FAA inspectors and the nature of the mechanical malfunction could not be determined. In a telephone interview with a Safety Board investigator, the pilot reported that the secondary shaft broke in half, resulting in a loss of drive power to the helicopter's main rotor. The pilot was aware of the advisory service bulletin issued by the kit manufacturer suggesting replacement of the secondary shaft assembly, but had not complied. Beginning in May 1995, the kit manufacturer released four separate Advisory Bulletins (A-23, A-26, A-32 and A-34) addressing installation, inspection, and shaft design change issues. Citing a history of secondary shaft failures, the most recent advisory bulletin at the time of the accident, issued May 2002, recommended replacement of the standard 30 mm secondary shaft with an upgraded 35 mm shaft.

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: 154 hours in all
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Injury: no injuries

The aircraft

  • Maximum gross weight: 1,500 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotorway RI 162 (piston); 0 hours total

The flight

  • Departed from: KRYN Tucson AZ at 6:40 pm
  • Destination: KRYN Tucson AZ
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 41°F (5°C)
  • Altimeter: 30.04 inHg

Injuries

FatalSeriousMinorNone
Crew1

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.