CHI01LA221 · Piper PA-30
Piper PA-30 · Accident: in flight collision with object en route
From BOD · Bowman, ND to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI01LA221
- 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
Piper PA-30
- Aircraft type
- Piper PA-30
- 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
- N7382Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From BOD · Bowman, NDTo 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
- En route · climb to cruise
- 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 › Altitude/clearance, not obtained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said they were dispatched on a routine cloud-seeding mission at 2250. All flight operations through takeoff were normal. The pilot said that after passing through 50 feet agl, the airplane would not climb. The pilot said he verified power on both engines and airspeed of 120 mph. He brought the gear up and the climb performance improved slightly. The pilot said, "The maximum altitude achieved was just below 3,100 feet msl (100 feet agl), as the rapidly increasing downdrafts from the invisible microburst soon overpowered any climb performance, and quickly pushed the aircraft downward as the VSI (vertical speed indicator) indication transitioned from slightly positive to 150+ fpm (feet per minute) negative." The pilot said the airplane's engines were at maximum power when they struck a tree approximately 1 mile from the departure end of the runway. The pilot said he pitched the nose up in preparation for the ground impact. The airplane broke free of the tree. The pilot said he leveled the wings, lowered the nose slightly to keep his speed up, and reduced the throttles to idle. The airplane touched down about 3 to 5 seconds after their collision with the tree. The pilot said that 1 minute after the crash, heavy rain from a thunderstorm occurred. An examination of the airplane revealed no anomalies. At 2253, the weather reported at Hettinger, North Dakota (HEI), 34 miles east of BPP, was few clouds at 8,000 feet agl, a broken ceiling of 12,000 feet agl, 10 miles visibility with light rain, winds 100 degrees at 9 knots, temperature 74 degrees Fahrenheit (F), dew point 68 degrees F, altimeter 29.80 inches of Mercury, and remarks, lighting in the distance west and northwest, rain began at 2245. At 2301, the weather reported at HEI was scattered clouds at 9,000 feet agl, a broken ceiling of 12,000 feet agl, 10 miles visibility with light thunderstorms and rain, winds 330 variable 030 at 8 knots, and remarks, lighting in the distance west to north, thunderstorms began at 2255. At 2322, the weather reported at HEI was 3,500 scattered, 10,000 broken, 12,000 overcast, 10 miles visibility with light thunderstorms and rain, winds 030 degrees at 32 knots, gusts to 41 knots, and remarks, peak wind 030 degrees at 41 knots recorded at 2317, wind shift at 2302, lightning in the distance all quadrants.
Probable cause
Altitude/clearance not obtained by the pilot during the initial climb. Factors relating to the accident were attaining the proper climb rate not being possible, the microburst, the dark night, and the tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01LA221
- Event ID
- 20010726X01523
- Case number
- CHI01LA221
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2001-07-21.
- API snapshot SHA-256: 7eed03eeb946f2789017ae61e84ec64ff130463e6e61d9c05b38813b917242a5; retrieved 2026-09-22T11:44:48.213Z.