CHI89DEC04 · Bridges LONG-EZ
Bridges LONG-EZ · Accident: on ground/water collision with terrain/water during takeoff
From Ray Community Airport (57D) to 7D2 · Troy, MI
Event
- NTSB case
- CHI89DEC04
- 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
Bridges LONG-EZ
- Aircraft type
- Bridges LONG-EZ
- 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
- N642JB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ray Community Airport (57D), New Haven, MITo 7D2 · Troy, MI
- 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 · roll/run
- 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
- On ground/water collision with terrain/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 › Unsuitable terrain or takeoff/landing/taxi area, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED THAT THE NOSE GEAR STRUCK SOMETHING ON THE RUNWAY DURING THE TAKEOFF ROLL. THERE WERE CHUNKS OF GRAVEL AND ASPHALT ON THE FIRST 800 FT OF THE RUNWAY. THE PILOT ATTEMPTED TO RETRACT THE NOSE GEAR BUT COULD NOT GET A FULL RETRACTION SO HE ELECTED TO FLY WITH IT PARTIALLY EXTENDED. A POWER REDUCTION WAS MADE TO 2000 RPM AT WHICH TIME THE AIRPLANE BEGAN TO VIOLENTLY VIBRATE. THE PILOT EXTENDED THE NOSE GEAR AND SHUT THE ENGINE DOWN IN PREPARATION FOR LANDING. THE NOSE GEAR COLLAPSED DURING THE LANDING. WITNESSES REPORTED SEEING SOMETHING FALLING FROM THE AIRPLANE DURING FLIGHT. EXAMINATION REVEALED A 20 INCH SECTION OF ONE PROPELLER BLADE WAS MISSING. THE WOODEN PROPELLER HAD A HISTORY OF DAMAGE WITH THE REPAIRS MADE BY THE PILOT.
Probable cause
THE PILOT'S DECISION TO TAKEOFF FROM UNSUITABLE TERRAIN WHICH RESULTED IN DAMAGE TO THE PROPELLER AND NOSE GEAR.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI89DEC04
- Event ID
- 20001213X28050
- Case number
- CHI89DEC04
- 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: 0055ebf8eeb3e1ae7db250caed62c3c5e5cba1932fed0d70decf5c411f867713; retrieved 2026-09-22T00:14:37.097Z.