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

Cessna 172S accident near Seattle, Washington, October 2, 2003

On October 2, 2003 at about 11:40 pm local time, a Cessna 172S, registered N350ME, was substantially damaged in an accident near Seattle, Washington (Boeing Field/King Co Intl). It was an instructional 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

Improper flare during the landing. Excessive airspeed and improper remedial action were factors.

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

What the record shows

Date
October 2, 2003 · about 11:40 pm local time
Place
Seattle, Washington · Boeing Field/King Co Intl · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172S · all 172Ss on the register
Registration
N350ME · no longer on the register · serial 172S8585
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The student pilot reported that when he turned to final approach, he realized that he was too high. The pilot pitched the nose down, but did not reduce power. Airspeed increased, and the pilot decided to slip the aircraft to slow down. The aircraft eventually got down to the VASI glide slope, but had an excessive airspeed for the landing. The aircraft touched down in a flat attitude and ballooned. The pilot pitched the nose down and the aircraft touched down on the nose gear and bounced. The pilot pitched the nose down and again the aircraft touched down on the nose gear and bounced. The aircraft eventually settled to the runway and the pilot applied braking action and pulled off the runway to conclude the flight. Post accident inspection of the aircraft revealed that the firewall had been substantially damaged.

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

Dual student

  • Certificate: student
  • Flight time: 73 hours in all; 49 in this make and model; 49 in the last 90 days; 21 in the last 30 days; 10 as pilot in command
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,574 hours
  • Last inspection: annual inspection, August 20, 2003; 82 hours since
  • Maximum gross weight: 2,200 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 0 hours total

The flight

  • Departed from: BFI Seattle WA at 11:30 pm
  • Flight plan: none
  • Runway 13L, 10,001 ft by 200 ft

Weather at the time

  • Light: daylight
  • Wind: at 3 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 2,300 ft
  • Temperature: 63°F (17°C), dew point 54°F (12°C)
  • Altimeter: 30.00 inHg
  • Observation at 11:53 pm from BFI

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.