The U.S. aircraft register, updated daily
Accidents · NTSB FTW82DA386 · Preliminary: the investigation is not finished

Grumman AA-5A accident near Tulsa, Oklahoma, September 22, 1982

On September 22, 1982 at about 4:30 pm local time, a Grumman AA-5A, registered N26171, was substantially damaged in an accident near Tulsa, Oklahoma (R.L. Jones Airport). It was an instructional 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 NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
September 22, 1982 · about 4:30 pm local time
Place
Tulsa, Oklahoma · R.L. Jones Airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Grumman AA-5A
Registration
N26171 · no longer on the register · serial AA5A-0463
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

THE STUDENT PILOT STATED THAT HE MADE SEVERAL TOUCH-AND-GO LANDINGS WITHOUT INCIDENT, WHEN THE ENGINE STARTED "CUTTING OUT" ON FINAL APPROACH. HE REPORTED THAT CARBURETOR HEAT WAS NOT APPLIED UNTIL AFTER THE POWER LOSS BEGAN. HE WAS UNABLE TO RESTORE POWER AND ELECTED TO MAKE A FORCED LANDING IN A PASTURE. AFTER MANEUVERING TO AVOID A FENCE AND A ROAD, THE LANDING GEAR SHEAR OFF DURING A CRASH LANDING AND THE PLANE SLID TO A STOP. THE ENGINE WAS REMOVED AND EXAMINED, BUT NO MECHANICAL REASON FOR A POWER LOSS WAS FOUND. DURING A SUBSEQUENT TEST RUN, THE ENGINE OPERATED NORMALLY.

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: student
  • Ratings: single-engine land
  • Flight time: 25 hours in all; 25 in this make and model; 15 in the last 90 days; 15 in the last 30 days; 2 as pilot in command
  • Medical certificate: Class 2 (valid medical--no waivers/lim.)
  • Seat: unk

The aircraft

  • Airframe total time: 2,841 hours
  • Last inspection: inspection type not recorded; 4 hours since
  • Maximum gross weight: 2,200 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320-E2G (piston); 0 hours total
  • Operator: Rivair Flying Service, INC.

The flight

  • Departed from: RVS Tulsa OK at 10:45 am
  • Destination: RVS Tulsa OK
  • Flight plan: none
  • Runway 18

Weather at the time

  • Light: daylight
  • Wind: from 200° at 10 knots
  • Visibility: 10 statute miles
  • Sky: not recorded; clear
  • Temperature: 176°F (80°C), dew point 0°F (-18°C)
  • Altimeter: 30.00 inHg
  • Observation at 11:32 am from RVS

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.

Other NTSB records under N26171 the same tail number, which may have belonged to a different aircraft at the time

1986-03-06ATL86LA086 · accident near Fayetteville, NC · substantial damage · no injuries

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.