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

Luscombe 8A accident near Logan, Utah, July 12, 1990

On July 12, 1990 at about 11:15 pm local time, a Luscombe 8A, registered N45537, was substantially damaged in an accident near Logan, Utah (Logan-Cache 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 PILOT'S FAILURE TO MAINTAIN DIRECTIONAL CONTROL AND HIS IMPROPER USE OF THE WHEEL BRAKES. A FACTOR RELATED TO THE ACCIDENT WAS: THE PILOT'S LACK OF EXPERIENCE IN THE MAKE AND MODEL OF AIRCRAFT.

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

What the record shows

Date
July 12, 1990 · about 11:15 pm local time · cases in 1990
Place
Logan, Utah · Logan-Cache · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Luscombe 8A · all 8As on the register
Registration
N45537 · no longer on the register · serial 2064
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

THE PILOT WAS FLYING THE AIRCRAFT TO LOGAN, UTAH FOR THE OWNER, HE HAD APPROXIMATELY 10 HOURS OF TOTAL TIME IN THE LUSCOMBE. HE REPORTED THAT AFTER LANDING ON RUNWAY 17 AND DURING THE ROLLOUT, THE AIRPLANE BEGAN TO 'WEATHERVANE SLIGHTLY.' SUBSEQUENTLY, AS THE PILOT WAS APPLYING WHEEL BRAKES, THE AIRPLANE NOSED OVER. AT 1650 MDT, THE WIND AT LOGAN WAS RPRTD TO BE FROM 180 DEG AT 5 KTS.

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: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 750 hours in all; 10 in this make and model
  • Medical certificate: Class 1 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Last inspection: inspection type not recorded
  • Maximum gross weight: 1,260 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Continental C-6S (piston); 0 hours total

The flight

  • Departed from: PIH Pocatello ID
  • Destination: LGU
  • Flight plan: none
  • Runway 17, 5,931 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 180° at 5 knots
  • Visibility: 40 statute miles
  • Sky: scat at 10,000 ft
  • Temperature: 99°F (37°C), dew point 46°F (8°C)
  • Altimeter: 30.00 inHg
  • Observation at 10:50 pm from LGU

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 N45537 the same tail number, which may have belonged to a different aircraft at the time

2000-11-25FTW01LA027 · accident near Antlers, OK · substantial damage · minor injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/DEN90LA162.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.