FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC95LA214 · Gillet C.P. 328

4 Sept 1995 · FIRE ISLAND, NY, United States

Gillet C.P. 328 · Accident: loss of control in flight while maneuvering

From Republic Airport (FRG) to an unrecorded destination

Report a problem

Event

NTSB case
NYC95LA214
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

Gillet C.P. 328

Aircraft type
Gillet C P 328
Category
Airplane
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
N4171G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Republic Airport (FRG), Farmingdale, NYTo 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
Maneuvering
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/spin
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

  • Copilot/second pilot › Aircraft control, not maintained
  • Pilot in command › Aircraft control, not maintained

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

NTSB narrative

The pilot/owner departed with another pilot for a local flight. About 25 minutes later, witnesses 3/4 mile off shore observed the airplane impact the water from a descending spin. Examination revealed no preimpact failure of the airplane or engine. The kit airplane was designed for aerobatic flight. The pilot/owner was not known to have performed aerobatic maneuvers. The other pilot owned an aerobatic airplane, and was known to have performed aerobatics. He had 1750 hours total time; 280 hours in a Pitts S-2 and 1 hour in this make and model. He was observed 2 hours earlier that day in another airplane performing aerobatics over the water near the area of the accident.

Probable cause

the failure of the pilots to maintain control of the airplane while performing aerobatics.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC95LA214
Event ID
20001207X04571
Case number
NYC95LA214
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: 425d68d1c4b18ba8a6de8ed8ddd2a2629be03d5c00ae305353cda924b0709ade; retrieved 2026-09-20T23:38:15.547Z.