NYC06CA225 · Piper PA-25-180
Piper PA-25-180 · Accident while standing
From South Jersey Regional Airport (VAY) to 1N4 · Woodbine, NJ
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC06CA225
- 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
Piper PA-25-180 Possible conflict
- Aircraft type
- Piper PA-25
- 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
- N6319Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From South Jersey Regional Airport (VAY), Mount Holly, NJTo 1N4 · Woodbine, NJ
- 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
- Standing · engine(s) start-up
- 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
- 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
- Pilot in command › Starting procedure, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After loading his equipment bag in the front seat of the airplane, the pilot pressed on each wing lift strut to verify that the brakes were set and then attempted to hand start the engine. He was able to start the engine, however; it "immediately came to full power." He then attempted to reach the cockpit, but was unable. The airplane moved forward, and struck a parked airplane. Both airplanes were substantially damaged. The pilot believed that when he placed his bag in the airplane, it may have "pushed the throttle forward." According to FAA publication FAA-P-8740-20, "No one should attempt to start an aircraft engine without a qualified person at the cockpit controls."
Probable cause
The pilot's improper starting procedure, which resulted in an uncontrolled taxi, and collision with a parked airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06CA225
- Event ID
- 20061027X01570
- Case number
- NYC06CA225
- 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, 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: cc5df9369d78efbdd00739c81b4a1882cc69856de2b41843fc4c0e46bba99249; retrieved 2026-09-22T04:25:27.305Z.