Piper PA-31T accident near Bismarck, North Dakota, May 4, 2005
On May 4, 2005 at about 2:00 am local time, a Piper PA-31T, registered N2338V, was substantially damaged in an accident near Bismarck, North Dakota (Bismarck Muni airport). It was a flight of an unrecorded kind under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Rupture of the hydraulic powerpak drain line which resulted in a loss of hydraulic fluid and the inability to properly lower the landing gear despite the pilot's execution of the emergency extension procedures. A contributing factor was the runway light struck during the emergency landing.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 4, 2005 · about 2:00 am local time · cases in 2005
- Place
- Bismarck, North Dakota · Bismarck Muni · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-31T · all PA-31Ts on the register
- Registration
- N2338V · registry record · serial 31T-8020049
- Damage
- Substantial damage
- Flight
- Flight of an unrecorded kind · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane was substantially damaged during an emergency landing when the landing gear did not extend properly. The pilot noted that when he attempted to lower the landing gear on approach to the intended destination nothing happened. He elected to divert to an airport with additional capabilities and assistance available. The pilot stated that he executed the emergency gear extension procedure, however, this procedure was not successful. The left main landing gear appeared to be fully extended, the nose landing gear was in a "dragging" condition, and the right main landing gear was retracted when observed by the tower controller prior to landing. The pilot noted that the red gear unlocked indicator light was illuminated and the green landing gear down/locked indicators were not illuminated. Since no further options were available to extend the gear, the pilot executed an emergency landing. The airplane touched down on the left main wheel which did not collapse initially. The right wing subsequently dropped and contacted the runway. The pilot applied left wheel brakes, however, the airplane departed the right side of the runway pavement and came to rest in the grass. The left main landing gear collapsed and a runway light was damaged in the process. The post-accident inspection revealed that a hydraulic powerpak drain line (Piper part number 46138-00) was ruptured. The drain line was located in the nose section of the airplane, forward of the cabin pressure bulkhead. The rupture was approximately one-half inch long. Hydraulic fluid was observed in the vicinity of the line rupture. The hydraulic reservoir was empty.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: private
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 6,778 hours in all; 397 in this make and model; 77 in the last 90 days; 42 in the last 30 days; 6,600 as pilot in command
- Last flight review: November 1, 2004
- Medical certificate: Class 3 (valid medical--no waivers/lim.)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 7,332 hours
- Last inspection: approved inspection programme, February 1, 2005; 50 hours since
- Maximum gross weight: 9,000 lb
- Seats: 8
- Landing gear: retractable
- Engine 1: Pratt & Whitney Canada PT6A-28 (turboprop); 0 hours total
- Engine 2: Pratt & Whitney Canada PT6A-28 (turboprop); 0 hours total
The flight
- Departed from: BJC Denver CO at 9:30 pm
- Destination: BIS Bismark ND
- Flight plan: IFR
- Runway 21, 6,600 ft by 100 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 48°F (9°C), dew point 9°F (-13°C)
- Altimeter: 30.00 inHg
- Observation at 1:52 am from BIS
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Connections how this case links to the rest of the register
- N2338V on the register today · the tail number may have moved to another aircraft since
- Piper PA-31 Navajo and Chieftain 934 registered today · the model family and its accident history
- Piper 44,848 aircraft on the register
- Engine: Pratt & Whitney Canada PT6A-28 13 aircraft carry this series today · as the NTSB recorded it
- Engine: Pratt & Whitney Canada PT6A-28 13 aircraft carry this series today · as the NTSB recorded it
- Bismarck Municipal · nearest airport
- Rocky Mountain Metro Airport · departed from
- Accidents and incidents in North Dakota 581 since 1982 · 59 in the last ten years
- North Dakota 2,495 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CHI05LA109.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
