GAA19CA180 · Piper PA23 250
Mtn Aviation Piper PA23 250 · Accident: birdstrike en route
From North Palm Beach County General Aviation Airport (F45) to Tampa International Airport (TPA)
Event
- NTSB case
- GAA19CA180
- 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 PA23 250
- Aircraft type
- Piper PA23
- 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
- N976AZ
- Operator
- Mtn Aviation
- Onboard fatalities
- Unknown
- Route
- From North Palm Beach County General Aviation Airport (F45), West Palm Beach, FLTo Tampa International Airport (TPA), Tampa, FL
- Aircraft age
- About 43 years (built 1976)
- 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 · descent
- Defining eventThe 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
- Birdstrike
- 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
- Environmental issues › Physical environment
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 of the multiengine airplane reported that, on a descending vector for a visual instrument landing system approach on an instrument flight rules flight plan, about 2,500 to 2,800 ft mean sea level, he "felt the aircraft shudder along with a loud bang." He then disengaged the autopilot to determine if the flight controls were affected and looked for damage on the wing and nose area; he saw no damage. The pilot continued to the airport and landed without further incident. During the landing, the pilot of a waiting aircraft reported that he saw damage to the accident airplane's vertical stabilizer that looked like a bird had hit it. During postaccident examination, blood and tissue were found on the airplane.
The airplane sustained substantial damage to the vertical stabilizer.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
An in-flight collision with a bird during the approach, which resulted in damage to the vertical stabilizer.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA180
- Event ID
- 20190325X85220
- Case number
- GAA19CA180
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 4bad9c2dc67c1bd4329ca5d09ad80406bb8bb118be68996891fae14aa5a92c05; retrieved 2026-09-16T08:41:19.510Z.