Piper PA-32RT-300T accident near Albany, Oregon, September 29, 1990
On September 29, 1990 at about 10:45 pm local time, a Piper PA-32RT-300T, registered N22450, was substantially damaged in an accident near Albany, Oregon (Albany airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
THE PILOT'S DECISION TO LAND WITH A STRONG TAILWIND RESULTED IN THE COLLAPSE OF THE LANDING GEAR.
Source: NTSB aviation accident database, copy made September 29, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 29, 1990 · about 10:45 pm local time
- Place
- Albany, Oregon · Albany · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32RT-300T PA-32RT-30 · all PA-32RT-300Ts on the register
- Registration
- N22450 · registry record · serial 32R-7887261
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
AT THE END OF A CROSS COUNTRY FLIGHT, THE PILOT APPROACHED THE RUNWAY WITH A 15-20 KNOT TAILWIND. THE AIRPLANE TOUCHED DOWN JUST PAST MID-FIELD AND DID NOT HAVE SUFFICIENT RWY TO STOP. THE PILOT ATTEMPTED TO TURN THE AIRPLANE OFF THE RUNWAY; HOWEVER, THE LANDING GEAR COLLAPSED. THERE WERE NO REPORTED MECHANICAL FAILURES OR MALFUNCTIONS WITH THE AIRPLANE AT THE TIME OF THE ACCIDENT.
The NTSB's narratives can run to many pages; this is the opening. Read the full report at the NTSB.
About this page
Everything above comes from the NTSB's public accident database and is rewritten in plain English only where the NTSB used codes; the probable cause and narrative are the NTSB's own words. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number SEA90LA198.
