FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03LA115 · Piper PA-46-350P

11 May 2003 · Brooksville, FL, United States

Piper PA-46-350P · Accident: in flight collision with object en route

From St. Petersburg Clearwater International Airport (KPIE) to an unrecorded destination

Report a problem

Event

NTSB case
MIA03LA115
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-46-350P

Aircraft type
Piper PA-46
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
N7KH
Operator
Unknown
Onboard fatalities
Unknown
Route
From St. Petersburg Clearwater International Airport (KPIE), St. Petersburg, FLTo not recorded
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 · climb to 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 collision with object
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

No findings designated as a cause are recorded in the NTSB data yet.

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 stated that after takeoff he performed airwork for approximately 1 hour then proceeded direct to the Hernando County Airport where he performed 2 or 3 practice instrument approaches. During climb out at 2,000 feet between 110 and 120 knots following another practice instrument approach, he noted a large bird fly past the windshield. He then felt an impact but there was no discrepancy with the flight controls. As the flight lesson was nearly complete, the flight proceeded to the departure airport where the airplane was landed uneventfully. The airplane was secured, then visually inspected which revealed a dent in the leading edge of the left horizontal stabilizer. He remained overnight at the airport, then departed the following day for an airport located along the east coast of Florida. The safety pilot reported that she was flying with the pilot to complete his annual recurrent training and after the initial departure proceeded to the Hernando County Airport to practice instrument approaches. The pilot-in-command had been holding at the published holding intersection (AZBOG), departed the holding pattern, began climbing, and while flying at 2,500 feet mean sea level and 120 knots indicated airspeed, collided with a bird. No effect on flight controls was noted and the flight proceeded to the initial departure airport where after landing, the external damage was noted. Examination of the airplane revealed the leading edge of the left horizontal stabilizer was crushed up near left butt line 38.177. Inspection revealed that canted frame assembly (p/n 84246-800), located at fuselage station 311.382, was torn adjacent to the forward attach bolt of the left horizontal stabilizer. Additionally, an angle (p/n 84218-2), which is riveted to and part of the canted frame assembly exhibited a section missing below and outboard of the forward attach bolt of the left horizontal stabilizer. Evidence of displacement between the forward attach bolt of the left horizontal stabilizer and the canted frame assembly was noted. Personnel from the Smithsonian National Museum of Natural History identified the bird to be the Black Vulture (Coryagyps atratus), which has a weight range between 42-75 ounces.

Probable cause

The in-flight collision with a Black Vulture resulting in substantial damage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA115
Event ID
20030610X00832
Case number
MIA03LA115
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: d9d2d1c56596c3b4482f6fac463c233465a0c0c6d9941ffdaf6fdb0729bc245d; retrieved 2026-09-22T09:18:47.673Z.