Cessna 177 accident near St. Johns, Arizona, August 16, 2008
On August 16, 2008 at about 10:45 pm local time, a Cessna 177, registered N3487T, was substantially damaged in an accident during initial climb near St. Johns, Arizona (St. Johns Industrial Airpark airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed and 2 people were seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 16, 2008 · about 10:45 pm local time · cases in 2008
- Place
- St. Johns, Arizona · St. Johns Industrial Airpark · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was killed and 2 people were seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 177 · all 177s on the register
- Registration
- N3487T · no longer on the register · serial 17700787
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.”
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
- Loss of engine power (partial) during initial climb defining event
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- factor Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Damaged/degraded other cases naming the engine
- cause Personnel issues › Action/decision › Action › Lack of action › Not specified
- factor Personnel issues › Action/decision › Action › Delayed action › Instructor/check pilot
- factor Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › High density altitude › Contributed to outcome
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
Pilot
- Certificate: flight instructor, commercial pilot
- Ratings: single-engine land; instructor: airplane single-engine; instrument: airplane
- Flight time: 1,081 hours in all; 7 in the last 90 days; 9 in the last 30 days; 790 as pilot in command; 587 on instruments
- Last flight review: December 28, 2006
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: rgt
- Injury: fatal
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 50 hours in all; 5 as pilot in command
- Last flight review: July 19, 2008
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 2,626 hours
- Last inspection: annual inspection, August 5, 2008; 2 hours since
- Maximum gross weight: 2,350 lb
- Seats: 4
- Landing gear: fixed
- Engine: Textron Lycoming O-320-E2D (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: SJN St. Johns AZ at 10:45 pm
- Destination: FFZ Mesa AZ
- Flight plan: VFR
- Runway 14, 5,322 ft by 75 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 280° at 8 knots, gusting 14
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 86°F (30°C), dew point 41°F (5°C)
- Altimeter: 30.04 inHg
- Observation at 10:54 pm from SJN
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | 1 | ||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
40 documents, released by the NTSB on July 24, 2009. 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.
Connections how this case links to the rest of the register
- N3487T: not on the register today · the record of its deregistration
- Cessna 177 Cardinal 2,158 registered today · the model family and its accident history
- Cessna 72,684 aircraft on the register
- Engine: Textron Lycoming O-320-E2D 258 aircraft carry this series today · as the NTSB recorded it
- St. Johns Industrial Air Park Airport · nearest airport
- Falcon Field · bound for
- Accidents and incidents in Arizona 2,985 since 1982 · 468 in the last ten years
- Arizona 8,422 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/SEA08LA179.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.
