ATL83FA366 · Pterodactyl/Lambert NONE
Pterodactyl/Lambert NONE · Accident: airframe, component or system failure
From Huntersville, NC to Charlotte, NC
Event
- NTSB case
- ATL83FA366
- 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
Pterodactyl/Lambert NONE
- 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
- N2084Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Huntersville, NCTo Charlotte, NC
- 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 91: General Aviation
- 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
- Unknown
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT WAS ON A X-COUNTRY ACCOMPANIED BY A PLT IN ANOTHER ULTRALIGHT VEHICLE. THE ACCIDENT ACFT WAS FASTER, SO THE PLT MANEUVERED AROUND WHILE EN ROUTE. DURING A TURN, THE ACCIDENT VEHICLE GOT OUT OF SIGHT FROM THE PLT OF THE OTHER VEHICLE & BECAME PERMANENTLY SEPARATED. AT 0957 EDT, A BOEING 727 CREW REPORTED A NEAR MISS WITH 2 ULTRALIGHTS IN THAT VICINITY. THE CAPTAIN ESTIMATED A SEPARATION OF APRX 100 FT. HOWEVER, HE OBSERVED THE ULTRALIGHTS AGAIN ABOUT 10 TO 15 SEC LATER & SAW NO EVIDENCE OF AN UPSET. AT ABOUT 1000 EDT, WITNESSES SAW THE LEFT WING OF THE ACCIDENT ACFT FOLD UPWARD, THEN HEARD A LOUD POP & SAW THE ULTRALIGHT FALL VERTICALLY TO THE GROUND. AN EXAM OF THE WRECKAGE REVEALED ONLY OVERLOAD FAILURES. REPORTEDLY, THE ULTRALIGHT WAS INVOLVED IN SOME TYPE OF MISHAP ON THE PREVIOUS DAY. THE CIRCUMSTANCES WERE NOT VERIFIED, BUT THE PROP & THE AXLE OF THE MAIN WHEELS REQUIRED REPLACING. DURING CONSTRUCTION, THEBUILDER HAD MADE MODIFICATIONS TO THE ACFT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83FA366
- Event ID
- 20001214X44408
- Case number
- ATL83FA366
- 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: e50ee342cd907d41475ba71f34920669b20d61db8cb73e5fcb710516b54d777f; retrieved 2026-09-21T06:11:36.266Z.