NYC07CA137 · Piper PA-28RT-201
Piper PA-28RT-201 · Accident: in flight collision with object during initial climb
From Hoge Farm Airport (56PA) to Bangor International Airport (BGR)
Event
- NTSB case
- NYC07CA137
- 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
- Instrument Meteorological Cond
Piper PA-28RT-201
- Aircraft type
- Piper PA-28
- 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
- N3023U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hoge Farm Airport (56PA), Tinicum, PATo Bangor International Airport (BGR), Bangor, ME
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The instrument-rated private pilot was attempting an early morning, short-field takeoff from a turf airstrip in a Piper PA-28RT-201. During the take-off roll, "mist blew into the departure end of the runway." The pilot continued the takeoff, and about 50 feet above the ground, the airplane impacted trees off the left side of the runway and flipped over. A fire department photograph, taken upon arrival at the airstrip, revealed the presence of fog about half way down the runway. The airstrip was 2,200 feet long and 100 feet wide, with trees on both sides.
Probable cause
The instrument-rated pilot's failure to maintain runway alignment by instruments after encountering fog during the initial climb. A factor was the foggy weather conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC07CA137
- Event ID
- 20070807X01133
- Case number
- NYC07CA137
- 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: f9f3a4a2ee61f8dccf451f8ef1097a91a0f41ec64ae4a20a95d8d60b2c856dbb; retrieved 2026-09-21T18:29:35.801Z.