FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC83FU003 · Pteradactyl ASCENDER

10 Apr 1983 · Girdwood, AK, United States

Pteradactyl ASCENDER · Accident: loss of control in flight en route

Report a problem

Event

NTSB case
ANC83FU003
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Pteradactyl ASCENDER

Category
Ultralight
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
UNREG
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 103: Ultralight
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · climb to cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Aircraft handling, not maintained
  • Pilot in command › Design stress limits of aircraft, exceeded

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

ACCORDING TO A WITNESS, THE ULTRALIGHT VEHICLE HAD JUST TAKEN OFF, HAD TURNED TO A DOWNWIND HEADING & WAS CLIMBING, WHEN IT BEGAN TO OSCILLATE LONGITUDINALLY. AFTER A FEW OSCILLATIONS, THE VEHICLE NOSED OVER, THE WINGS FOLDED & THE ULTRALIGHT CRASHED TO THE GROUND. ALL PARTS OF THE ULTRALIGHT WERE ACCOUNTED FOR & AN EXAM REVEALED THAT THE FRACTURES WERE INDICATIVE OF OVERLOAD FAILURES. REPORTEDLY, THE PLT HAD ONLY ABOUT 5 TO 10 HRS IN THIS MAKE & MODEL. ACCORDING TO THE PLT'S FRIENDS, THEY HAD HEARD HIM TALK ABOUT HAVING TO HOLD THE NOSE DOWN DURING FLT. THEY STATED HE HAD A TENDENCY TO 'BURY THE AIRSPEED' WHILE FLYING. ACCORDING TO OTHER PLTS THAT HAVE FLOWN THIS ULTRALIGHT VEHICLE, THE PTERODACTYL CAN ACHIEVE 55 KTS WITH ONLY SLIGHTLY OVER HALF THROTTLE, IT BECOMES INCREASINGLY PITCH SENSITIVE AT HIGH SPEEDS & IT REQUIRES EXCESSIVE NOSE DOWN PITCH CONTROL ABOVE 55 KTS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ANC83FU003
Event ID
20001214X42578
Case number
ANC83FU003
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 1dea18ab6954e53a0c448ab9dfa6b36fc8e217ebd6b47ae4cb0e56347da3b1f9; retrieved 2026-09-21T06:56:25.431Z.