FTW00LA066
2000-01-17 · BROWNSVILLE, Texas, United States · None · 1 aircraft · Status: Completed
Airport BRO
Aircraft involved
Probable cause & findings
The hard landing of the aircraft resulting from the pilot's excessive rate of descent on the VFR approach. A factor was the loss of right engine power for an undetermined reason.
Factual narrative
On January 17, 2000, at 1041 central standard time, a Cessna 340A twin-engine airplane, Mexican registration, XBBJU, was substantially damaged during a hard landing at the Brownsville International Airport, Brownsville, Texas. The Mexican commercial pilot, sole occupant, was not injured. Visual meteorological conditions prevailed and a flight plan was not filed for the 14 Code of Federal Regulations Part 91 ferry flight. The cross-country flight originated from Victoria, Mexico, at 0800. According to the airport manager, the pilot stated that he was having "problems with the right engine" while inbound to Brownsville. The airport's tower controller cleared the airplane to land on the active runway. The pilot; however, stated that he was going to land on runway 35 instead. Runway 35 was closed at the time of the landing and, according to the airport manager, workers were on the runway during the airplane's landing. The wind at the time of the landing was from 150 degrees at 9 knots. The airport manager added that while on short final the airplane sank and landed "very hard" at the runway threshold. The airport manager stated that all six of the propeller blades displayed impact damage. Both wings were structurally damaged outboard of the engine nacelles. A post accident inspection conducted by an FAA inspector revealed that both propellers were bent in nearly the same manor "indicating that both engines were turning almost the same during impact." Visual inspection of the right engine showed no anomalies. Fuel was found in the right engine's fuel line, and the cylinders produced "good compression." The engine's tachometer generator was removed and inspected, and no anomalies were noted. In the Pilot/Operator Aircraft Accident Report, NTSB form 6120.1/2, the pilot stated under the section "How Could This Accident Been Prevented" that he should have continued ahead instead of returning to runway 35 after the engine failed. On the downwind leg of the VFR approach to runway 13R, the pilot reported a loss of right engine power. The pilot elected to land on runway 35. The airplane descended and landed 'very hard' on the runway. Both wings were bent downward outboard of the engine nacelles. A post accident inspection of the right engine revealed no anomalies. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_FTW00LA066.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗