# Accident 19990406019609A: Beech 58, Nashville, TN, April 6, 1999 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: April 6, 1999, 04:50 local time - Place: Nashville, TN - Airport: Nashville International Airport - Damage: Substantial damage - Phase of flight: Final Approach - Operating rules: Air taxi and commuter (Part 135) - Operator: PA9A - Location: 36.1245° N, 86.6782° W: Placed by OpenAirDocs at NASHVILLE INTL (BNA), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=36.1245&lon=-86.6782&mi=10 - Aircraft: N80UL, a cancelled registration (https://openairdocs.org/deregistered/N80UL-2003-08-20) (OpenAirDocs) - Registry model: Beech 58 (registry code 1152740, https://openairdocs.org/model/beech-58) (OpenAirDocs) - Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs) - Reported make and model: BEECH 58 - Reported engine: CONT IO520CB - Fatal injuries: 0 - Pilot flight hours: 1,353 total, 176 in this make and model, 176 in the last 90 days - NTSB investigation: [NTSB ATL99LA069](https://openairdocs.org/ntsb/ATL99LA069) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/19990406019609A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON APRIL 6, 1999, AT 0450 CENTRAL DAYLIGHT TIME, A BEECH 58, N80UL, COLLIDED WITH THE GROUND AND BURST INTO FLAMES DURING AN INSTRUMENT APPROACH TO RUNWAY 2C AT THE NASHVILLE INTERNATIONAL AIRPORT IN NASHVILLE, TENNESSEE. THE CARGO FLIGHT WAS OPERATED BY PARAGON AIR EXPRESS INC., UNDER THE PROVISIONS OF TITLE 14 CFR PART 135 WITH AN INSTRUMENT FLIGHT PLAN FILED. VISUAL WEATHER CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. THE AIRPLANE SUSTAINED SUBSTANTIAL DAMAGE. THE COMMERCIAL PILOT RECEIVED MINOR INJURIES. THE FLIGHT DEPARTED MEMPHIS, TENNESSEE, AT 0340. THE PILOT REPORTED THAT UPON ARRIVING IN THE NASHVILLE AREA, THE APPROACH CONTROLLER ISSUED HIM AN APPROACH CLEARANCE TO RUNWAY 2C. WHILE ON FINAL APPROACH, THE PILOT RECALLED THAT THERE WERE RAIN SHOWERS AND HIGH WINDS ASSOCIATED WITH THUNDERSTORM ACTIVITY IN THE IMMEDIATE VICINITY OF THE APPROACH FACILITIES. UPON REALIZING THAT HIS FINAL APPROACH WAS ALTITUDE TOO HIGH, THE PILOT REQUESTED A 2L LANDING; THE CONTROLLER CLEARED THE FLIGHT TO LAND ON RUNWAY 2L. THE AIRPLANE COLLIDED WITH THE GROUND AS THE PILOT MEAEUVERED FOR A LANDING BACK TO RUNWAY 2C. EXAMINATION OF THE ACCIDENT SITE DISCLOSED THAT THE AIRPLANE RE STED ABOUT 200 YARDS LEFT OF THE APPROACH END OF RUNWAY 2C, AND ORIENTED ON A SOUTHWEST HEADING. THERE WAS EXTENSIVE FIRE DAMAGE TO BOTH OUTBOARD PANELS OF THE WING ASSEMBLY. THE PILOT DID NOT REPORT A MECHANICAL PROBLEM WITH THE AIRPLANE DURING THE FLIGHT. THE PILOT REPORTED EXPERIENCING MODERATE RAIN AND STRONG WINDS OUT OF THE NORTHWEST WHILE MANEUVERING FOR THE LANDING. (-23) NARRATIVE STATES "SEE ATTACHED PILOT STATEMENT" BUT NO STATEMENT ATTACHED. (.4) THE APPROACH CONTROLLER ISSUED THE PILOT AN APPROACH CLEARANCE TO THE CENTER RUNWAY. WHILE ON FINAL APPROACH, THE PILOT RECALLED THAT THERE WERE RAIN SHOWERS AND HIGH WINDS ASSOCIATED WITH THUNDERSTORM ACTIVITY IN THE IMMEDIATE VICINITY OF THE APPROACH FACILITIES. UPON REALIZING THAT HIS FINAL APPROACH ALTITUDE WAS TOO HIGH, THE PILOT REQUESTED A LANDING ON AN ADJACENT RUNWAY. THE CONTROLLER CLEARED THE FLIGHT TO LAND ON THE REQUESTED RUNWAY. THE AIRPLANE COLLIDED WITH THE GROUND AS THE PILOT MANEUVERED FOR A LANDING BACK TO THE ORIGINAL RUNWAY. EXAMINATION OF THE ACCIDENT SITE DISCLOSED THAT THE AIRPLANE RESTED ABOUT 200 YARDS LEFT OF THE APPROACH END OF THE RUNWAY. THERE WAS EXTENSIVE FIRE DAMAGE TO BOTH OUTBOARD PANEL S OF THE WING ASSEMBLY. THE PILOT DID NOT REPORT A MECHANICAL PROBLEM WITH THE AIRPLANE DURING THE FLIGHT. THE PILOT REPORTED EXPERIENCING MODERATE RAIN AND STRONG WINDS OUT OF THE NORTHWEST WHILE MANEUVERING FOR THE LANDING. A REVIEW OF THE AVAILABLE RUNWAYS AT THE AIRPORT REVEALED THAT RUNWAY 31 WAS AVAILABLE AND IS 11,000 FEET LONG. THE PREVAILING WINDS AT THE TIME OF THE ACCIDENT WERE 300 DEGREES AT 19 KNOTS WITH WIND GUST TO 20 KNOTS. ACCORDING TO THE FLIGHT MANUAL FOR THE BEECH 58, THE CROSS WIND COMPONENT IS APPROXIMATELY 19 KNOTS. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB ATL99LA069](https://openairdocs.org/ntsb/ATL99LA069), Apr 6, 1999: Beech 58 (N80UL), Nashville, TN, substantial damage. Probable cause: The pilot's inflight decision to land on a runway with a strong cross wind, rather then on a runway into the wind. A factor was the strong cross wind conditions. From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.