Cessna 172S N350ME
2 October 2003 · Seattle, Washington, United States · No injuries
Summary
On 2 October 2003 at about 23:40 local time, a Cessna 172S registered N350ME, operated by Galvin Flying Service, was involved in an accident near Seattle, Washington, United States. One person was on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 23:40
- Classification
- Accident
- Location
- Seattle, Washington, United States
- Nearest airport
- Boeing Field/King Co Intl (BFI)
- Coordinates
- 47.5167, -122.3033
- Aircraft
- Cessna 172S
- Registration
- N350ME
- Category
- Airplane
- Engines
- 1
- Operator
- Galvin Flying Service
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Instructional
- Phase of flight
- Not recorded
- Route
- Seattle → Unknown
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- SEA04LA002
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 0 | 0 | 0 | 1 |
Probable cause
Improper flare during the landing. Excessive airspeed and improper remedial action were factors.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Other Cessna 172 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 25 Dec 2003 | Cessna 172RG | Key West, Florida, United States | Avion Jet Center, LLC | No injuries | - |
| 16 Mar 2003 | Cessna 172N | Foley, Minnesota, United States | - | Fatal | 3 |
| 12 Jul 2003 | Cessna 172S | Chandler, Arizona, United States | Angel Air | No injuries | - |
| 18 Jan 2003 | Cessna 172 | Chesapeake, Virginia, United States | - | No injuries | - |
| 21 Mar 2003 | Cessna 172S | Monroe, Georgia, United States | Elite Flight Center | Fatal | 2 |
| 22 Aug 2003 | Cessna 172S | Lake Elmo, Minnesota, United States | Wings, Inc. | Fatal | 3 |
All 12,209 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 10 Nov 2003 | Cessna 150C | Toledo, Washington, United States | - | No injuries | - |
| 12 Jun 2003 | Rockwell S-2R | Royal City, Washington, United States | - | No injuries | - |
| 2 Oct 2003 | Cessna 340 | Blakely Island, Washington, United States | - | Minor injuries | - |
| 17 Jan 2003 | Classic Fighter ME-262 REPRODUCTION | Everett, Washington, United States | Wolfgang Czaia | No injuries | - |
| 15 Jun 2003 | Cessna 172P | Seattle, Washington, United States | - | No injuries | - |
| 10 Jul 2003 | Hanks AVID FLYER | Toledo, Washington, United States | - | Serious injuries | - |