FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD98LA083 · Maule M-5-235C

23 Jul 1998 · NEWBURG, ME, United States

Maule M-5-235C · Accident: in flight collision with object during initial climb

From No airport to an unrecorded destination

Report a problem

Event

NTSB case
IAD98LA083
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-5-235C

Aircraft type
Maule M-5
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
N5643V
Operator
Unknown
Onboard fatalities
Unknown
Route
From No airportTo 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
Initial climb
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
In flight collision with object
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
Tree(s)
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
  • Pilot in command › Proper alignment, not maintained

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

During the takeoff ground roll on runway 36, the airplane veered off the left side of the runway and collided with trees. Examination of the accident site by an FAA Inspector revealed deep, ground scars similar to the tailwheel on the grass strip in the run-up area. There were ground scars similar to the main landing gear on the wet, tall, unmowed grass strip, for about 800 feet where the airplane accelerated on the runway, then the ground scars veered off to the left in the vicinity of the trees. The pilot said he ruled out any on ground directional correction, '...the wind caused a further drift to the left of 36 and put the aircraft in a direct path to the tree line...it was my intention to climb over the trees. Though the engine sounds indicated no anomalies, it just didn't seem to be delivering normal thrust...I came to the conclusion that clearing the trees would not be an option...I therefore opted for a controlled crash into the trees.' The pilot reported that there was no mechanical malfunction with the airplane.

Probable cause

The pilot's failure to maintain directional control. Related factors were the long, wet, unmowed grass runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD98LA083
Event ID
20001211X10612
Case number
IAD98LA083
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: 52d61d4b6ec6b865f93f325c332469adba435dab84554e7543a01c410ed8231b; retrieved 2026-09-21T20:45:07.508Z.