The U.S. aircraft register, updated daily
Accidents · NTSB LAX08LA080 · Final report

Piper PA-31-350 accident near Portland, Oregon, March 20, 2008

On March 20, 2008 at about 5:26 pm local time, a Piper PA-31-350, registered N4098A, was substantially damaged in an accident during landing near Portland, Oregon (Portland airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The failure of company maintenance personnel to install the upper pivot bolt through the pivot hole in the upper end of the landing gear actuating rod, and the company maintenance inspector's inadequate inspection of the work performed.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 20, 2008 · about 5:26 pm local time · cases in 2008
Place
Portland, Oregon · Portland · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-31-350 · all PA-31-350s on the register
Registration
N4098A · registry record · serial 31-8152200
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

The NTSB's narrative final · quoted from the NTSB record

The pilot reported that when he was preparing to land at his destination, he found that the right main landing gear failed to extend. The pilot diverted back to the originating airport. Maintenance personnel discussed the problem with the pilot and various remedial actions were tried without success. The pilot declared an emergency, and landed with the right main gear retracted. During the recovery efforts, the airplane was jacked up in order to extend the right main landing gear, which locked in place. The airplane was then towed to a hangar. Examination revealed that the upper pivot bolt had not been installed through the pivot hole in the upper end of the actuating rod during recent maintenance. The mechanic who did the repair and the inspector who signed off the repair did not detect the discrepancy.

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

What happened, in order

  1. Landing gear not configured during landing defining event

The NTSB's findings

  • cause Aircraft › Aircraft systems › Landing gear system › Gear extension and retract sys › Incorrect service/maintenance other cases naming the landing gear
  • Aircraft › Aircraft systems › Landing gear system › Gear extension and retract sys › Inoperative other cases naming the landing gear
  • cause Personnel issues › Task performance › Maintenance › Installation › Maintenance personnel
  • cause Personnel issues › Task performance › Inspection › Post maintenance inspection › Maintenance personnel

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
  • Flight time: 1,500 hours in all; 300 in this make and model; 280 in the last 90 days; 110 in the last 30 days; 1,375 as pilot in command
  • Last flight review: January 1, 2008
  • Medical certificate: Class 2
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 16,547 hours
  • Last inspection: approved inspection programme, March 1, 2008; 3 hours since
  • Maximum gross weight: 7,000 lb
  • Seats: 2
  • Landing gear: retractable
  • Engine 1: Lycoming TSIO-540-J2B (piston); 0 hours total
  • Engine 2: Lycoming TSIO-540-J2B (piston); 0 hours total
  • Operator: Ameriflight LLC

The flight

  • Departed from: PDX Portland OR at 2:45 pm
  • Destination: RBG Roseburg OR
  • Flight plan: IFR
  • Runway 03, 7,001 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 200° at 9 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 2,400 ft; scat at 1,800 ft
  • Temperature: 46°F (8°C), dew point 37°F (3°C)
  • Altimeter: 30.18 inHg
  • Observation at 4:48 pm from PDX

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Other NTSB records under N4098A the same tail number, which may have belonged to a different aircraft at the time

1989-10-25LAX90LA036 · accident near Ontario, CA · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
  • N4098A 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,840 aircraft on the register
  • Engine: Lycoming TSIO-540-J2B · as the NTSB recorded it
  • Engine: Lycoming TSIO-540-J2B · as the NTSB recorded it
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/LAX08LA080.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.