FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18FA206 · Piper PA60 602P

30 Jul 2018 · Greenville, ME, United States

Piper PA60 602P · Accident: aerodynamic stall/spin while maneuvering

From Pembroke Airport (CYTA) to Charlottetown Airport (CYYG)

Report a problem

Event

NTSB case
ERA18FA206
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
3 · 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

Piper PA60 602P

Aircraft type
Piper PA60
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
C-GRRS
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pembroke Airport (CYTA), PembrokeTo Charlottetown Airport (CYYG), Charlottetown
Aircraft age
About 36 years (built 1982)
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
Non-U.S., Non-Commercial
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
Maneuvering
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
Aerodynamic stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot of the multiengine airplane was in cruise flight at 23,000 ft mean sea level (msl) in day visual meteorological conditions when he reported to air traffic control that the airplane was losing altitude due to a loss of engine power. The controller provided vectors to a nearby airport; about 7 minutes later, the pilot reported the airport in sight and stated that he would enter a downwind leg for runway 14. By this time, the airplane had descended to about 3,200 ft above ground level. Radar data indicated that the airplane proceeded toward the runway but that it was about 400 ft above ground level on short final. The airplane flew directly over the airport at a low altitude before entering a left turn to a close downwind for runway 21. Witnesses stated that the airplane's propellers were turning, but they could not estimate engine power. When the airplane reached the approach end of runway 21, it entered a steep left turn and was flying slowly before the left wing suddenly "stalled" and the airplane pitched nose-down toward the ground.

Postaccident examination of the airplane and engines revealed no mechanical deficiencies that would have precluded normal operation at the time of impact. Examination of both propeller systems indicated power symmetry at the time of impact, with damage to both assemblies consistent with low or idle engine power. The onboard engine monitor recorded battery voltage, engine exhaust gas temperature, and cylinder head temperature for both engines. A review of the recorded data revealed that about 14 minutes before the accident, there was a jump followed by a decrease in exhaust gas temperature (EGT) and cylinder head temperature (CHT) for both engines. The temperatures decreased for about 9 minutes, during which time the right engine EGT data spiked twice. Both engines' EGT and CHT values then returned to normal, consistent with both engines producing power, for the remaining 5 minutes of data. It is possible that a fuel interruption may have caused the momentary increase in both engines' EGT and CHT values and prompted the pilot to report the engine power loss; however, the engine monitor did not record fuel pressure or fuel flow, and examination of the airplane's fuel system and engines did not reveal any mechanical anomalies. Therefore, the reason for the reported loss of engine power could not be determined.

It is likely that the pilot's initial approach for landing was too high, and he attempted to circle over the airport to lose altitude. While doing so, he exceeded the airplane's critical angle of attack while in a left turn and the airplane entered an aerodynamic stall at an altitude too low for recovery.

Probable cause

The pilot's exceedance of the airplane's critical angle of attack while maneuvering to land, which resulted in an aerodynamic stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18FA206
Event ID
20180731X41318
Case number
ERA18FA206
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. 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: 02f61791814d4e196438892a71b75d9a6c2e058f319c531b160c9240198906df; retrieved 2026-09-15T06:45:03.466Z.