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

Teman MONO-FLY accident near Congress, Arizona, November 10, 1983

On November 10, 1983 at about 7:30 pm local time, a Teman MONO-FLY (ultralight), registered UNREG, was substantially damaged in an accident near Congress, Arizona. It was a personal flight under ultralight rules (Part 103). 1 person was seriously injured. 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
November 10, 1983 · about 7:30 pm local time
Place
Congress, Arizona · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Teman MONO-FLY
Registration
UNREG · no longer on the register
Damage
Substantial damage
Flight
Personal flight · ultralight rules (Part 103)

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

REPORTEDLY, THE PLT WAS ON HIS 1ST FLT IN THE ULTRALIGHT VEHICLE AFTER HE HAD BEEN TAXIING IT DURING THE PREVIOUS WEEK. DURING TAKEOFF FROM A RANCH, THE VEHICLE COLLIDED WITH THE GROUND. ACCORDING TO THE DEPUTY SHERIFF, WHO RESPONDED TO THE SCENE, THE PLT STATED THAT THE CONTROLS FAILED TO RESPOND & HE WAS UNABLE TO LEVEL THE VEHICLE FROM A LEFT BANK. THE PLT REFUSED TO COOPERATE WITH THE INVESTIGATOR. HE SAID HE HAD SOLD THE VEHICLE & DID NOT KNOW WHERE IT WAS LOCATED.

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
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: unk

The aircraft

  • Last inspection: inspection type not recorded
  • Seats: 1
  • Landing gear: fixed
  • Engine: Unknown UNKNOWN (type not recorded); 0 hours total

The flight

  • Flight plan: none
  • Runway 0

Weather at the time

  • Light: daylight
  • Wind: from 150° at 6 knots
  • Visibility: 30 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 0°F (-18°C)

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 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

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.