FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW90FA170 · Air & Space 18A

29 Aug 1990 · Shreveport, LA, United States

Faa (BTR Fsdo) Air & Space 18A · Accident: loss of control on ground/water during takeoff

From Shreveport Regional Airport (SHV) to an unrecorded destination

Report a problem

Event

NTSB case
FTW90FA170
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
0 · 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

Air & Space 18A

Aircraft type
Air Space 18
Category
Gyroplane
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
N6132S
Onboard fatalities
Unknown
Route
From Shreveport Regional Airport (SHV)To 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 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
Takeoff
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 on ground/water
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 › Procedures/directives, not followed

Approximate · Estimated position: the centre of Shreveport, LA, the place the record names. Not the accident site.

NTSB narrative

THE PIC STATED THAT AT LIFTOFF A SEVERE LATERAL VIBRATION OCCURRED CAUSING LOSS OF CONTROL OF THE GYROPLANE. WITNESSES REPORTED AN ERRATIC PORPOISING PITCHING MOTION. THE AIRCRAFT CAME TO REST APPROXIMATELY 1,500 FEET AFTER CONTROL WAS LOST, WHICH WAS AT THE POINT OF ATTEMPTED LIFTOFF. AS A RESULT OF FLAPPING, TWO OF THE THREE ROTOR BLADES CONTACTED THE PROPELLER AND RUDDER. ALTHOUGH NOT RECOMMENDED BY THE MANUFACTURER, THE FRONT SEAT WAS OCCUPIED BY A PILOT RATED PASSENGER WITH NO GYROPLANE EXPERIENCE. DURING SUBSEQUENT FLIGHT TESTING, TAKEOFF WAS PERFORMED UNDER SIMILAR CONDITIONS. IMPROPER TECHNIQUES DURING ATTEMPTED LIFTOFF RESULTED IN ERRATIC OSCILLATION AND ROTOR RPM DECAY. NO MECHANICAL MALFUNCTION WAS DISCOVERED.

Probable cause

FAILURE OF THE PILOT IN COMMAND TO FOLLOW PUBLISHED TAKEOFF PROCEDURES.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW90FA170
Event ID
20001212X24005
Case number
FTW90FA170
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: e0c25486ade87d0b8594d9e1c01c669e34fea9a6b84d6409c1bf75bf717b423c; retrieved 2026-09-23T05:22:13.179Z.