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

Piper PA-32-301T accident near Long Beach, California, March 27, 2005

On March 27, 2005 at about 10:40 pm local time, a Piper PA-32-301T, registered N8243L, was substantially damaged in an accident near Long Beach, California (Long Beach airport). It was a personal flight under general aviation rules (Part 91). 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 pilot's failure to maintain directional control during the landing rollout.

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

What the record shows

Date
March 27, 2005 · about 10:40 pm local time
Place
Long Beach, California · Long Beach · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-32-301T · all PA-32-301Ts on the register
Registration
N8243L · registry record · serial 32-8024035
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The airplane veered off the runway and impacted signs during the landing rollout. The pilot reported that during the flight no mechanical malfunctions were experienced with his airplane, and he had performed a routine landing on runway 30. Within seconds after touchdown, the airplane veered left. The pilot attempted to straighten out the airplane's course, but he was not successful. The pilot also indicated that his loss of control surprised him, and his reaction time was slow. No vibration or shimmy was noted at any time during the landing rollout. Runway 30 is 10,000 feet long and 200 feet wide. At the time of the mishap, the surface wind was from 170 degrees at 5 knots. No other airplanes were in the area. The airplane's brake and steering systems were subsequently examined, and no evidence of any mechanical malfunction was found.

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: single-engine land; instrument: airplane
  • Flight time: 1,022 hours in all; 729 in this make and model; 3 in the last 90 days; 3 in the last 30 days; 968 as pilot in command; 0 on instruments
  • Last flight review: April 1, 2004
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,731 hours
  • Last inspection: annual inspection, April 1, 2004; 95 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming TIO-540 (piston); 0 hours total

The flight

  • Departed from: SBA Santa Barbara CA at 9:45 pm
  • Destination: LGB Long Beach CA
  • Flight plan: IFR
  • Runway 30, 10,000 ft by 200 ft

Weather at the time

  • Light: daylight
  • Wind: from 170° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 39°F (4°C)
  • Altimeter: 29.97 inHg
  • Observation at 10:53 pm from LGB

Injuries

FatalSeriousMinorNone
Crew1

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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.