# NTSB CHI99LA195: Cessna 150G, N2263J, Fort Scott, KS, June 25, 1999 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 25, 1999, 12:05 local (17:05 UTC) - Place: Fort Scott, KS - Coordinates: 37.829967, -94.699028 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.8300&lon=-94.6990&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report January 18, 2001 - Report: Approved by Office Director - NTSB case key (mKey): 46673 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI99LA195 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/46673/pdf - Page: https://openairdocs.org/ntsb/CHI99LA195 ## Probable cause The pilot's failure to maintain directional control during the landing roll. A factor to the accident was the soft terrain condition. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - roll - directional control - not maintained, pilot in command (cause) - On ground/water encounter with terrain/water, landing - roll - terrain condition - soft (contributing factor) - Nose over, landing - roll ## Analysis On landing rollout the airplane veered to the left side of the runway. The pilot reported that the airplane departed the runway surface, the tires sunk into soft turf on the side of the runway, and the airplane nosed over coming to rest in an inverted position. Inspection of the runway surface revealed a single tire skid mark that initiated approximately 240 feet from the runway threshold, 10 feet left of the runway centerline, and followed a left curved path terminating approximately 465 feet from the runway threshold, 20 feet left of the runway edge. The tire skid mark was approximated 225 feet long. Inspection of the wreckage revealed no mechanical anomalies with the aircraft's control and the brake systems. Both main landing gear wheels were free moving and the brake system was exercised and operated without any anomalous behavior. ## Factual narrative On June 25, 1999, at 1205 central daylight time, a Cessna 150G, N2263J, owned and piloted by a private pilot, sustained substantial damage after a loss of control and subsequent nose over during a landing on Runway 17 (4,400 feet by 75 feet, dry/asphalt) at the Fort Scott Municipal Airport, Fort Scott, Kansas. Visual meteorological conditions prevailed at the time of the accident. The personal flight was operating under the provisions of 14 CFR Part 91 and was not on a flight plan. The pilot and one passenger reported no injuries. The flight departed Butler Memorial Airport, Butler, Missouri, at 1130. According to the pilot's written statement, on landing rollout the airplane veered to the left side of the runway. The pilot reported that the airplane departed the runway surface, the tires sunk into soft turf on the side of the runway, and the airplane nosed over coming to rest in an inverted position. Inspection of the runway surface revealed a single tire skid mark that initiated approximately 240 feet from the runway threshold, 10 feet left of the runway centerline, and followed a left curved path terminating approximately 465 feet from the runway threshold, 20 feet left of the runway edge. The tire skid mark was approximated 225 feet long. Federal Aviation Administration (FAA) inspection of the wreckage revealed no mechanical anomalies with the aircraft's control and the brake systems. Both main landing gear wheels were free moving and the brake system was exercised and operated without any anomalous behavior. ## Aircraft - Registration: [N2263J](https://openairdocs.org/aircraft/N2263J), registered now, S/N 15065463, built 1966 (OpenAirDocs) - Reported make and model: Cessna 150G - Registry model: [Cessna 150G](https://openairdocs.org/model/cessna-150g) (registry code 2071816) (OpenAirDocs) - Registry engine: [Continental 0-200 series](https://openairdocs.org/engine/continental-0-200-series) (registry code 17020, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 150-65463 - Airframe hours: 3518 - Engines: Lycoming O-320-E2D 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Edwin Harry Shoafstall - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 17, 1999, 15 hours before - Departed: BUM, BUTLER, MO - Destination: FSK - Airport: FSK, Fort Scott Municipal Arpt, runway 17, 4,400 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 59; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 655 total, 25 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 160° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 77 °F, dew point 70 °F - Altimeter: 29.00 inHg - Observed at: CNU, 35 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 19990625007699A](https://openairdocs.org/incident/19990625007699A), Jun 25, 1999: Cessna 150G, Fort Scott, KS, Substantial damage. Pilot lost control of the acft during a crosswind landing, the left wheel left the rwy, the wingtip struck the ground, and the acft nosed over stopping… ## Other investigations on N2263J (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 CHI94LA035](https://openairdocs.org/ntsb/CHI94LA035), Nov 9, 1993: Cessna 150G (N2263J), Neosho, MO, substantial damage. Probable cause: THE PILOT-IN-COMMAND'S FAILURE TO MAINTAIN DIRECTIONAL CONTROL DURING LANDING ROLLOUT. 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.