CHI07CA194 · Boeing N2S-3
Boeing N2S-3 · Accident: in flight collision with terrain/water while maneuvering
From Trenton Municipal Airport (TRX) to an unrecorded destination
Event
- NTSB case
- CHI07CA194
- 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
Boeing N2S-3
- Aircraft type
- Boeing N2
- 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
- N1178J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Trenton Municipal Airport (TRX), Trenton, MOTo 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
- In flight 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 › Altitude/clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was substantially damaged when it impacted water while maneuvering. The pilot stated that he was "positioning [the airplane] on downwind for a low approach to runway 18" while following another airplane that was conducting a low approach. The pilot reported that while he was attempting to "level off" the "elevator froze," preventing him from leveling off. One witness stated that she saw the airplane attempt to complete a loop. Another witness, who was a certified flight instructor, stated that he saw the airplane in a near vertical descent prior to flying below tree top level. The airplane subsequently impacted water east of the airport. An inspection after the accident revealed no mechanical anomalies which would have prevented normal operation of the airplane.
Probable cause
The pilot's failure to maintain sufficient altitude/clearance above the water while maneuvering. A factor in the accident was the low altitude maneuver attempted by the pilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA194
- Event ID
- 20070810X01170
- Case number
- CHI07CA194
- 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: 6e7f3b041c4fc9149a24608dd81a9771b93553f3b167c8b05db139e4edbaa43d; retrieved 2026-09-21T18:28:06.284Z.