FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD02LA054 · Miller Barnet J4B-2

26 May 2002 · Manville, NJ, United States

Miller Barnet J4B-2 · Accident: loss of control in flight during landing

From Central Jersey Regional Airport (47N) to Central Jersey Regional Airport (47N)

Report a problem

Event

NTSB case
IAD02LA054
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
Unknown
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

Miller Barnet J4B-2

Aircraft type
Miller BARNET J4B-2
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
N8121M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Central Jersey Regional Airport (47N), Manville, NJTo Central Jersey Regional Airport (47N), Manville, NJ
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
Landing · flare/touchdown
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 › Flare, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot of the gyrocopter had conducted several touch and go's on the runway. On his last approach, he aligned the gyrocopter with the grass apron, and elected to continue on his heading to land on the grass adjacent to the runway. Witnesses described the approach as "fast" and "odd" and that the gyrocopter pitched nose-down before hitting the ground and rolling over. The pilot had 200 hours of flight experience. He did not possess a rating or a student endorsement for rotorcraft/gyrocopter, and had no experience in make and model. The pilot reported that there were no mechanical anomalies with the gyrocopter.

Probable cause

The pilot's improper flare prior to touchdown. A factor was the pilot's lack of experience in aircraft type, make, and model.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD02LA054
Event ID
20020606X00812
Case number
IAD02LA054
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, coordinates. 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: 8457f71ec67e959585e89c61fdd835cbba3620683a4ca147a2c7ccfea81f535f; retrieved 2026-09-21T19:43:22.015Z.