FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14CA385 · Cote James RANS S 6S

4 Aug 2014 · New Berlin, PA, United States

Cote James RANS S 6S · Accident during initial climb

From Sauers-Haven Airport (4PA1) to Sauers-Haven Airport (4PA1)

Report a problem

Event

NTSB case
ERA14CA385
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
0 · 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

Cote James RANS S 6S

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
N502CW
Onboard fatalities
Unknown
Route
From Sauers-Haven Airport (4PA1), New Berlin, PATo Sauers-Haven Airport (4PA1), New Berlin, PA
Aircraft age
About 7 years (built 2007)
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
Miscellaneous/other
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 systems
  • Personnel issues › Task performance

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

NTSB narrative

The pilot stated that just after takeoff, the airplane entered "uncoordinated flight to the left." He applied right rudder to correct, but felt that the rudder was ineffective. After clearing trees at the end of the runway, the pilot elected to conduct a precautionary landing in a field. He stated that the airplane's rate of descent was "high," and that the nose landing gear collapsed upon touchdown. The airplane subsequently nosed over and came to rest inverted. Postaccident examination revealed substantial damage to the engine firewall, both wings, and the vertical stablilizer. Examination of the rudder controls revealed no anomalies. According to the pilot, his passenger was "apprehensive" about the flight, and inadvertently applied pressure to the left rudder pedal with his foot throughout the takeoff and accident sequence.

Probable cause

The passenger's inadvertent interference with the rudder controls during the takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14CA385
Event ID
20140814X65019
Case number
ERA14CA385
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: db48ce85e5fb61d611bf136f0c23b20b4786e304888c0acbd755ae942f6c60f4; retrieved 2026-09-16T01:38:39.458Z.