FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08LA179 · Cessna 177

16 Aug 2008 · St. Johns, AZ, United States

Cessna 177 · Accident: loss of engine power (partial) during initial climb

From St Johns Industrial Air Park (SJN) to Falcon Field (FFZ)

Report a problem

Event

NTSB case
SEA08LA179
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 177

Aircraft type
Cessna 177
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N3487T
Onboard fatalities
Unknown
Route
From St Johns Industrial Air Park (SJN), St. Johns, AZTo Falcon Field (FFZ), Mesa, AZ
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Initial climb
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power (partial)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The certified flight instructor (CFI), pilot undergoing instruction (PUI), and one passenger were departing from an airport with a density altitude of 8,690 feet mean sea level. The fuel tanks were filled to maximum capacity, and the estimated gross weight was about 130 pounds less than the maximum gross weight. During the takeoff, a witness at the airport observed that as the airplane traveled down the runway there was no change in engine sound. The witness further stated that as the airplane lifted out of ground effect , it did not climb any higher. It continued down the runway and at its end, the witness saw the airplane stall and turn to the left, prior to ground impact. The PUI reported that during the takeoff, “We used virtually the entire runway for takeoff.” The PUI was focused on obstacles ahead of the runway and notified the CFI that they had cleared the obstacles. The PUI indicated that the CFI then assumed control of the airplane and entered the airplane into a climb to clear additional obstacles. The PUI stated that as the flight controls were pulled back it felt like they had less available power, most likely due to the attitude of the airplane. The airplane then collided with obstacles. Post accident engine examination showed that the intake lifter for the Number 4 cylinder camshaft lobe was worn and the follower was heavily pitted. Both the intake and exhaust lifter for the Number 3 cylinder were heavily scored and the corresponding camshaft lobes were heavily worn. While the exact amount of degradation to the engine's power output could not be established, the alteration of the cam lobe profile will alter the amount and duration of the valve opening, thus affecting power output. The engine was overhauled 10 years prior to the accident and had accrued about 330 hours during this time. Although the engine's storage history for the last 10 years could not be determined, the amount of corrosion and pitting found make it highly likely that the internal engine components corroded due to inadequate lubrication resulting from lack of consistent operation. Lycoming Service Letter L180B states that, "Engines in aircraft that are flown only occasionally may not achieve normal service life because of corrosion." A Lycoming publication states that, “Corrosion is a known cause of tappet and cam lobe wear. The engines of aircraft that are not flown regularly may be extremely vulnerable to corrosion...Once started, the process is not likely to stop until it reaches a point where these parts are doing an unacceptable job.”

Probable cause

The failure of both pilots to abort the takeoff when a suitable climb rate could not be attained. Contributing to the accident was the reduction of available power due to the camshaft lobe and lifter corrosion/wear, the high density altitude, and the CFI’s inadequate supervision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08LA179
Event ID
20080818X01259
Case number
SEA08LA179
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 3699dcda92e8ad1ffb6e58e4dae478a7ea8e0de76dcfdc7c01549fb21264cc36; retrieved 2026-09-13T19:21:28.431Z.