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

Quicksilver MXL II accident near Cave Junction, Oregon, September 9, 1992

On September 9, 1992 at about 11:30 pm local time, a Quicksilver MXL II (ultralight), registered UNREG, was substantially damaged in an accident near Cave Junction, Oregon. It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

THE PILOT'S POOR VISUAL LOOKOUT. FACTORS INCLUDE A STATIC WIRE IN THE AREA OF FLIGHT.

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

What the record shows

Date
September 9, 1992 · about 11:30 pm local time · cases in 1992
Place
Cave Junction, Oregon · map
Type
Accident
Injuries
2 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Quicksilver MXL II · all MXL IIs on the register
Registration
UNREG · registered outside the United States · serial 320
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

THE PILOT OF THE TWO PLACE ULTRALIGHT WAS CRUISING OVER A RIVER CANYON WHEN THE AIRCRAFT IMPACTED A STATIC WIRE WHICH THE PILOT HAD NOT SEEN.

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

  • Flight time: 150 hours in all; 150 in this make and model
  • Medical certificate: None
  • Seat: unk

The aircraft

  • Airframe total time: 95 hours
  • Last inspection: inspection type not recorded, January 2, 2000
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 582 (piston); 0 hours total

The flight

  • Flight plan: none
  • Runway 0

Weather at the time

  • Light: daylight
  • Wind: at 10 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 75°F (24°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.

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

2026-07-07CEN26LA246 · accident near Hooker, OK · substantial damage · minor injuries
2026-02-28CEN26LA131 · accident near Van Burensburg, IL · substantial damage · no injuries
2025-10-13ERA26LA017 · accident near Gaffney, SC · substantial damage · serious injuries
2025-09-27CEN25LA397 · accident near Harvard, IL · substantial damage · no injuries
2025-09-12CEN25LA385 · accident near Rossville, IN · substantial damage · serious injuries
2025-07-07CEN25LA242 · incident near Ingram, TX · minor damage · no injuries
2025-06-18DCA25WA305 · accident near N/A · serious injuries
2025-05-01OPS25LA034 · incident near Washington, DC
2025-04-11CEN25LA155 · accident near Brady, TX · substantial damage · serious injuries
2025-01-30DCA25MA108 · accident near Washington, DC · destroyed · fatal

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/SEA92LA202.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.