FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Northeast Aviation Piper PA-23-250 accident

5 May 2003 · Buffalo, NY, United States

Piper PA-23-250 · Accident: loss of control in flight on approach

From Dutchess County Airport (POU) to Buffalo Niagara International Airport (BUF)

Report a problem

Event

NTSB case
NYC03LA097
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
Charter & commuter
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-23-250

Aircraft type
Piper PA-23
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
N448VP
Onboard fatalities
Unknown
Route
From Dutchess County Airport (POU), Poughkeepsie, NYTo Buffalo Niagara International Airport (BUF), Buffalo, NY
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 135: Air Taxi & Commuter
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
Approach · VFR pattern final
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
Stall/mush
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 › Airspeed, not maintained

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 was approaching to land on runway 23 with a tower reported wind from 170 degrees at 10 knots. He reported that at 20 feet, and an airspeed of 100-110 mph, the airplane fell to the runway. The airport was equipped with a low level windshear detection system. According to data from 2 minutes before the accident to 2 minutes after the accident, from the on-airport sensors, the wind was variable by 40 degrees, and the velocity changed by about 5 knots.

Probable cause

The pilot's failure to maintain sufficient airspeed to prevent an inadvertent stall. Factors were the variable and gusty winds.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC03LA097
Event ID
20030514X00662
Case number
NYC03LA097
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: d81ff8dbeabb557e3fca8df1a5d090a7bb5c8e9fbb49e503d9a93e5490fbc2c2; retrieved 2026-09-18T15:49:58.911Z.
  • The NTSB's operator name is blank for N448VP; the operator shown is the name the NTSB's other records give its FAA operator code, NAHA.