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

Amateur-built STARDUSTER II SA300 accident near San Jose, California, July 19, 2011

On July 19, 2011 at about 4:50 pm local time, a amateur-built STARDUSTER II SA300, registered N411TM, was substantially damaged in an accident during landing (landing roll) near San Jose, California (Reid Hillview 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 decision to not follow the designated taxiway, and failure to maintain clearance from a sign.

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

What the record shows

Date
July 19, 2011 · about 4:50 pm local time · cases in 2011
Place
San Jose, California · Reid Hillview · 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
Amateur-built STARDUSTER II SA300
Registration
N411TM · no longer on the register · serial 1
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

During the landing roll, as the pilot approached the end of the runway, he decided to cut the corner from the runway to the taxiway. He said the airplane collided with a sign that he did not see. The collision resulted in substantial damage to the underside of the right wing, and the lower right wing spars were broken and separated. He said that there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation.

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. Miscellaneous/other during landing (landing roll) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during taxi (from runway)

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › (general) › Decision related to condition
  • cause Environmental issues › Physical environment › Object/animal/substance › Sign/marker › Response/compensation

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 320 hours in all; 70 in this make and model; 39 in the last 90 days; 21 in the last 30 days; 240 as pilot in command
  • Last flight review: June 2, 2011
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 629 hours
  • Last inspection: annual inspection, November 11, 2010; 70 hours since
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming IO-360 SER (piston); 0 hours total

The flight

  • Departed from: KRHV San Jose CA
  • Destination: KRHV San Jose CA
  • Flight plan: none
  • Runway 31R, 3,100 ft by 75 ft

Weather at the time

  • Light: night, dark
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 68°F (20°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew1

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

6 documents, released by the NTSB on August 22, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

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

2014-08-17WPR14FA348 · accident near Placerville, CA · substantial damage · fatal

Connections how this case links to the rest of the register

Aircraft
Place
Record

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