# Accident 20100227039999A: Cessna 340A, Grove City, PA, February 27, 2010

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 27, 2010, 11:30 local time
- Place: Grove City, PA
- Airport: Grove City
- Damage: Substantial damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 41.1461° N, 80.1678° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=41.1461&lon=-80.1678&mi=10
- Aircraft: N1952E, a cancelled registration (https://openairdocs.org/deregistered/N1952E-2018-05-30) (OpenAirDocs)
- Registry model: Cessna 340A (registry code 2076405, https://openairdocs.org/model/cessna-340a) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: CESSNA 340A
- Reported engine: CONT MOTOR TSIO-520 SER
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 1,208 total, 10 in this make and model, 27 in the last 90 days
- NTSB investigation: [NTSB ERA10CA231](https://openairdocs.org/ntsb/ERA10CA231) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100227039999A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

I CONTACTED ^PRIVACY DATA OMITTED^ TO CONFIRM THAT HE WAS THE PILOT IN COMMAND OFN1952E THAT WAS INVOLVED IN THE AIRCRAFT ACCIDENT AT THE GROVE CITY AIRPORT  (29D) ON THE DATE OF FEBRUARY 27, 2010. ^PRIVACY DATA OMITTED^ VERIFIED HE WAS FLYING N1952E ON THE AFOREMENTIONED DATE.  FLIGHT ORIGINATED AT THE HARRISBURG CAPITAL CITY AIRPORT PENNSYLVANIA (CXY) TO GROVE CITY AIRPORT PENNSYLVANIA (29G). PER ^PRIVACY DATA OMITTED^, HE WAS ON AN IFR FLIGHT PLAN THAT HE FILED WITH DUATS AND HAD ALSO RECEIVED A WEATHER BRIEFING FROM THAT SOURCE. THE FLIGHT PLAN ALTITUDE WAS 6,000 FEET AND ONCE IN COMMUNICATION WITH YOUNGSTOWN APPROACH CONTROL, HE WAS CLEARED FOR THE GPS 28 AT GROVE CITY AIRPORT, WITH NO FIELD CONDITIONREPORT.  WHEN ^PRIVACY DATA OMITTED^ WAS INSTRUCTED TO CONTACT THE GROVE CITY AIRPORTUNICOM FREQUENCY, HE DID SO.  HOWEVER, HE INDICATED NO ONE ANSWERED HIS CALLS, SO HE DECIDED TO CALL THE HERTZ RENTAL CAR AGENCY LOCATED ON THE FIELD TO DETERMINE THE WEATHER CONDITIONS AT THE AIRPORT. ^PRIVACY DATA OMITTED^ INDICATED HE BROKE OUT AT APPROXIMATELY 2,000 FEET AND DID A LOW PASS ABOVE THE AIRPORT TO TRY TO DETERMINE THE DEPTH OF THE SNOW; CONVINCED THAT IT WAS A COUPLE OF INCHES DEEP, HE CIRCLED AND ATTEMPTEDTO LAND. ONCE ON THE RUNWAY, THE SNOW WAS DEEPER THAN ANTICIPATED.  ^PRIVACY DATA OMITTED^ STATED THAT, ON THE ROLLOUT,  APROXIMATELY 1,500 TO 2,000 FEET DOWN THE RUNWAY, HE DECIDED IT WAS SAFER TO LAND THAN TO GO-AROUND. THE AIRPLANE THEN STARTED TO DRIFT TO THE RIGHT OF THE RUNWAY AND HIT A SNOW BANK WITH THERIGHT ENGINE STOPPING IT, SPINNING THE EMPENNAGE CLOCKWISE INTO THE SNOWBANK, AND STOPPING 180 DEGREES FROM ITS ORIGINAL POSITION.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ERA10CA231](https://openairdocs.org/ntsb/ERA10CA231), Feb 27, 2010: Cessna 340A (N1952E), Grove City, PA, substantial damage. Probable cause: The pilot's failure to maintain directional control after electing to land on a snow-covered runway.

## Other reports on N1952E (1)

Matched to the same aircraft by N-number and date.

- [Accident 20150316010559A](https://openairdocs.org/incident/20150316010559A), Mar 16, 2015: Cessna 340A (N1952E), Butler, PA, Substantial damage. On Monday, March 16, 2015, N1952E, a Cessna model 340A went off the end of runway 26 at Butler county airport, Butler, PA, and came to rest at the bottom of…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.