NYC89LA219 · Piper PA-22
Piper PA-22 · Accident: in flight encounter with weather en route
From N31 · Kutztown, PA to N63 · STROUNDSBURG, PA
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC89LA219
- 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
- Instrument Meteorological Cond
Piper PA-22
- Aircraft type
- Piper PA-22
- 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
- N2467A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From N31 · Kutztown, PATo N63 · STROUNDSBURG, PA
- 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
- En route · cruise
- 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
- In flight encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › Planning/decision, improper
- Pilot in command › VFR flight into imc, inadvertent
- Terrain condition › Soft
Approximate · Estimated position: the centre of Montague, NJ, the place the record names. Not the accident site.
NTSB narrative
THE PILOT DEPARTED GEORGETOWN, DELAWARE FOR MT POCONO, PENNSYLVANIA. HE LANDED AT CHESWOLD, DELAWARE, WHERE HE RECEIVED UPDATED WEATHER FROM MILLVILLE AUTOMATED FSS. THE PILOT DEPARTED AGAIN, BUT DIVERTED TO KUTZTOWN, PENNSYLVANIA, LANDED AND REFUELED. HE ATTEMPTED TO CONTINUE THE FLIGHT TO MT POCONO; HOWEVER, ADVERSE WEATHER PRECLUDED A LANDING AND HE CONTINUED EAST NORTHEAST. THE WEATHER CONTINUED TO DETERIORATE AND THE PILOT DECIDED TO LAND IN AN OPEN FIELD. DURING THE LANDING ROLL, THE NOSE GEAR SETTLED INTO SOFT MUD AND THE AIRCRAFT FLIPPED OVER.
Probable cause
IMPROPER PLANNING/DECISION BY THE PILOT WHICH RESULTED IN HIS INADVERTENT FLIGHT INTO INSTRUMENT METEOROLOGICAL CONDITIONS (IMC). FACTORS RELATED TO THE ACCIDENT WERE: THE ADVERSE WEATHER CONDITIONS AND SOFT TERRAIN IN THE EMERGENCY LANDING AREA.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC89LA219
- Event ID
- 20001213X29484
- Case number
- NYC89LA219
- 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: be55e1a357e61067fcf14cf2bcbf29a3472a987a9e6b75f0727d1ad4834b13a1; retrieved 2026-09-22T00:02:13.261Z.