NTSB CAROL · Event
Event SEA04LA002
Aircraft involved
Probable cause & findings
Improper flare during the landing. Excessive airspeed and improper remedial action were factors.
Factual narrative
On October 2, 2003, about 1640 Pacific daylight time, a Cessna 172S, N350ME, registered to a private individual and operated by Galvin Flying Service as a 14 CFR Part 91 solo instructional flight, was substantially damaged during landing at Boeing Field, Seattle, Washington. Visual meteorological conditions prevailed at the time and no flight plan was field for the local flight. The student pilot, the sole occupant, was not injured. In a written statement, the student pilot reported that he took off on runway 13 left with the intent on staying in the pattern to practice touch-and-go landings. The student stated that while on downwind, he was cleared to land. The student reduced power and extended one notch of flaps. Base and final approach turns were made with additional power reduction and flap extension. The student pilot stated that when he turned to final approach, he realized that he was too high. The student lowered the nose of the aircraft, but did not reduce power. Airspeed began to increase and the student attempted to "slip to slow down." The student eventually got the aircraft on the VASI glide slope, but had an indicated airspeed of 75 knots. The student pilot then reduced power and continued to land with 70 to 75 knots airspeed. The aircraft touched down in a flat attitude with excessive airspeed and ballooned. The pilot pitched the nose down and the aircraft touched down on the nose gear and bounced. The student pitched the aircraft down and again the aircraft touched down on the nose gear and bounced. The aircraft finally settled to the runway and the pilot applied braking action and eventually pulled off the runway. The student pilot then taxied back to the fixed base operator to conclude the flight. On October 9, 2003, representatives from Galvin Flying service reported that the firewall sustained substantial damage. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_SEA04LA002.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type. Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2016 · Conference paper
Early Morning Concurrent Session: Aviation Management and Operations: Presentation: Analysis of Factors Related to True Airspeed (TAS) Calculation Utilizing the Handicap Procedure for the 2015 Women's Air Race Classic
In most post-WWII cross country air racing events, the “handicap” method of determining race scoring is utilized. A typical example is the Women’s Air Race Classic transcontinental annual competition.…
- Embry-Riddle Scholarly Commons 2015 · Conference paper
Approach Stability from FDM Data
The Embry-Riddle Aeronautical University Prescott Campus maintains a fleet of twenty four aircraft, which includes sixteen Cessna 172S NavIII and four Diamond DA42NG equipped with flight data monitori…
Browse the full corpus — academia portal ↗