NYC99FA160 · Piper J3C-65
Piper J3C-65 · Accident: loss of control in flight during initial climb
From Dawson, MD (no airport) to New Castle International Airport (VA85)
Event
- NTSB case
- NYC99FA160
- 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
- 0
- 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 J3C-65
- Aircraft type
- Piper J3
- 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
- N29832
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dawson, MD (no airport)To New Castle International Airport (VA85), New Castle, VA
- 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
- First occurrenceThe 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 control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command › Altitude/clearance, inadequate
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Three Piper J3s, departed an airport in a valley with higher terrain nearby, and a density altitude of about 3,000 feet. Each airplane turned toward rising terrain, consisting of lower finger ridges and canyons, and a higher main ridge. The first airplane carrying only a pilot climbed faster than the terrain, and turned downwind. The second and third airplanes each carrying a pilot and passenger, tried to follow similar paths. The second airplane was at gross weight, and the pilot reported he encountered descending air which drove him down into the trees. The pilot reported no engine or airplane problems. The airplane was equipped with a cruise propeller which increased cruise speed and decreased the airplane's rate of climb. The pilots had been briefed on alternate departure routes that would not have required an immediate climb over rising terrain, but they were not used. FAA publications advised of the need to download weight when operating with higher density altitudes, and to approach ridgelines at a 45 degree angle to allow for escape in case of turbulence or descending air.
Probable cause
was the pilot's improper decision to turn toward rising terrain with inadequate terrain clearance. Factors were the density altitude, and unfavorable winds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99FA160
- Event ID
- 20001212X19086
- Case number
- NYC99FA160
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: d254a677fb4847c604223b4d33e9fea73881da8df15bf49ac76fb557fc7a543b; retrieved 2026-09-21T10:57:54.394Z.