FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD00LA030 · Maule M-4-220C

31 Mar 2000 · Lincoln Park, NJ, United States

Maule M-4-220C · Accident: loss of control on ground/water during landing

From Lincoln Park Airport (N07) to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

Maule M-4-220C Possible conflict

Aircraft type
Maule M-4
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
N2060U
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lincoln Park Airport (N07)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
Landing
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 › Aircraft control, not maintained

Approximate · Estimated position: the centre of Lincoln Park, NJ, the place the record names. Not the accident site.

NTSB narrative

During a stop and go landing, the airplane ground looped, veered off to the right, and struck a parked airplane. The pilot reported no mechanical deficiencies. Winds at the time were from 070 degrees at 10, gusting to 15 knots. The pilot reported a total time of 170 hours; 78 hours in tail wheel airplanes, and 9 hours in make and model. He also reported that he had ground-looped the airplane 8 months prior to this accident.

Probable cause

the pilot's failure to maintain control during landing roll. A factor was the crosswind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD00LA030
Event ID
20001212X20653
Case number
IAD00LA030
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: 59420865f0e72fc9173c33eb3e2878adc2a7b10de4f6f3b11f276b515c43abf2; retrieved 2026-09-21T10:40:19.267Z.