# NTSB LAX03LA262: Cessna 182, N6250A, Brownsville, CA, August 25, 2003 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: August 24, 2003, 18:11 local (Aug 25, 2003, 01:11 UTC) - Place: Brownsville, CA - Coordinates: 39.455276, -121.291664 - Nearby events: https://openairdocs.org/map.md?lat=39.4553&lon=-121.2917&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: Serious injuries - Injuries: 2 serious - Status: Completed, report December 28, 2004 - Report: Approved by Office Director - Parties: WP-SAC-FSDO - NTSB case key (mKey): 57774 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX03LA262 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/57774/pdf - Page: https://openairdocs.org/ntsb/LAX03LA262 ## Probable cause The pilot's improper flare and his failure to maintain directional control. Contributing factors were excessive airspeed, pilot-induced oscillation, and inadequate recovery from a bounced landing. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Hard landing, landing - flare/touchdown - flare - improper, pilot in command (cause) - airspeed - excessive, pilot in command (contributing factor) - Loss of control - on ground/water, landing - flare/touchdown - porpoise/pilot-induced oscillation - inadvertent, pilot in command (contributing factor) - directional control - not maintained, pilot in command (cause) - recovery from bounced landing - inadequate, pilot in command (contributing factor) - airport/facilities - narrow - On ground/water encounter with terrain/water, landing - roll - terrain condition - berm - terrain condition - drop-off/descending embankment ## Analysis The airplane landed hard and veered off the runway. During the approach the pilot was flying faster than normal. About 300-feet after the runway designation marking, the airplane touched down with very little flare. The airplane began to porpoise down the 20-foot wide runway. The airplane departed off the left side of the runway and collided with a berm. It continued down a slope and slid about 200-feet, with the airplane's wings colliding with several small trees. The airplane nosed over and came to rest inverted, leaving both the pilot and passenger hanging upside down. The passenger, who was also a pilot, reported no pre-impact mechanical malfunctions or failures with the airplane. ## Factual narrative On August 24, 2003, at 1811 Pacific daylight time, a Cessna 182, N6250A, landed hard and veered off the runway at Brownsville Airport (Q21), Brownsville, California. The owner/pilot was operating the airplane under the provisions of 14 CFR Part 91. The private-pilot and the one passenger, also a private-pilot, sustained serious injuries; the airplane sustained substantial damage. Day visual meteorological conditions prevailed, and no flight plan had been filed. The local flight departed Brownsville about 1745. In a written statement, the passenger reported that the purpose of the flight was to test new radio equipment that had been installed on the airplane. During the approach to runway 24, he noted that the pilot was flying faster than normal. About 300-feet after the runway designation marking, the airplane touched down with very little flare. The airplane began to porpoise down the 20-foot wide runway. The passenger told the pilot to go-around, but the pilot responded by saying it was too late. The airplane departed off the left side of the runway and collided with a berm. It continued down a slope and slid about 200-feet, with the airplane's wings colliding with several small trees. The airplane nosed over and came to rest inverted, leaving both men hanging upside down. They were taken in a helicopter to the nearest hospital and treated for their serious injuries. During the accident the airplane incurred damage to both wings and the bottom of the fuselage. The passenger stated that the accident could have been prevented if he and the pilot had made an agreement prior to the flight that the pilot would relinquish controls to him when asked. He reported no pre-impact mechanical malfunctions or failures with the airplane. ## Aircraft - Registration: [N6250A](https://openairdocs.org/deregistered/N6250A-2013-04-29), registration cancelled 2013-04-29, S/N 33050, built 1956 (OpenAirDocs) - Reported make and model: Cessna 182 - Registry model: [Cessna 182](https://openairdocs.org/model/cessna-182) (registry code 2072702) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 33050 - Engines: Continental O-470 reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 1, 2002 - Departed: Q21, Brownsville, CA - Airport: Q21, Brownsville, runway 24, 2,320 × 20 ft, gravel ## Flight crew As NTSB recorded them. NTSB leaves out names. - Co-pilot; age 74; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; last flight review September 4, 2002; seat: right; flight hours: 750 total, 6 in this make and model - Pilot; age 94; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, unknown; seat: left ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 91 °F, dew point 54 °F - Altimeter: 29.88 inHg - Observed at: KOVE, 15 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20030824020819A](https://openairdocs.org/incident/20030824020819A), Aug 24, 2003: Cessna 182, Brownsville, CA, Substantial damage. (-23) Aircraft departed Q21 (Brownsville Aero Pines) for local 91 flight to test newly installed radios. The 94-year-OLD private pilot/owner, with expired… 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. --- 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.