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

Beech 95-B55 accident near Petaluma, California, November 19, 1999

On November 19, 1999, a Beech 95-B55, registered N550RT, was substantially damaged in an accident near Petaluma, California (Petaluma Muni airport). It was a personal flight 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

The failure of the pilot to maintain adequate airspeed which resulted in a stall/mush condition and subsequent hard landing.

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

What the record shows

Date
November 19, 1999
Place
Petaluma, California · Petaluma Muni · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Beech 95-B55 · all 95-B55s on the register
Registration
N550RT · no longer on the register · serial TC-2101
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot was attempting a short field landing and allowed the airspeed to dissipate too soon. The airplane entered a stall/mush condition and landed hard. The force of the landing bent the engine mounts and broke the wings. The pilot reported that he had not experienced any mechanical problems with the aircraft. The airplane was equipped with vortex generators on the wings and vertical stabilizer, which, according to the STC developer, reduces the stall, approach and Vmca airspeeds by at least 10 knots. The various reference speed reductions were never approved for inclusion as a supplement to the Pilot's Operating Handbook (POH). The STC developer said that pilots were supposed to use the original speeds and limitations in the POH. The pilot said he was using an approach speed derived from a sales brochure from the STC maker. The pilot stated that the accident could have been prevented by maintaining 'greater speed.'

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: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 4,150 hours in all; 300 in this make and model; 20 in the last 90 days; 1 in the last 30 days
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Last inspection: annual inspection, September 1, 1999
  • Maximum gross weight: 5,100 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Continental IO-470-L (piston); 0 hours total

The flight

  • Departed from: STS Santa Rosa CA
  • Destination: O69
  • Flight plan: none
  • Runway 11, 3,600 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 050° at 6 knots
  • Visibility: 20 statute miles
  • Sky: overcast at 20,000 ft; not recorded
  • Temperature: 57°F (14°C), dew point 45°F (7°C)
  • Altimeter: 30.00 inHg
  • Observation at 8:55 am from SUU, 32 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

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.