CHI05LA128
2005-05-28 · Smith Center, Kansas, United States · None · 1 aircraft · Status: Completed
Airport K82
Aircraft involved
Probable cause & findings
Failure of the Piper airplane pilot to obtain visual separation from the Cessna airplane rolling out after landing on the intersecting runway resulting in a collision between the two aircraft. Contributing factors were the evasive maneuver attempted by the pilot of the Cessna and the runway light struck during that maneuver.
Factual narrative
On May 28, 2005, about 1100 central daylight time, a Cessna T210N, N6366Y, piloted by a private pilot, sustained substantial damage, and a Piper PA-25-235, N9886P, piloted by a commercial pilot, was undamaged, when they collided at the intersection of runway 35 and runway 14 at Smith Center Municipal Airport (K82), Smith Center, Kansas. The Cessna was rolling out after landing on runway 35 (3,601 feet by 50 feet, asphalt) and the Piper was landing on runway 14 (2,453 feet by 75 feet, turf) when the accident occurred. The Cessna was being operated on a personal flight under 14 CFR Part 91. The Piper was returning from a local aerial application flight under 14 CFR Part 137. Neither flight was on a flight plan at the time of the accident. Visual meteorological conditions prevailed. The pilot and passenger on-board the Cessna and the pilot on-board the Piper were not injured. The Cessna pilot reported that he made several position reports on the common traffic advisory frequency (CTAF) as the flight approached K82. He stated that he entered the traffic pattern and landed on runway 35. He reported that as the aircraft was rolling out after landing he observed the second aircraft landing on runway 14 to his immediate left. He noted that the second aircraft passed in front of his Cessna. He stated that he applied brakes and "swerved hard to the left," but was unable to avoid a collision. The Cessna pilot reported that his aircraft departed the left side of the pavement "slightly" where it struck a runway light before he regained control. The Piper pilot reported that some showers were passing through the area. He noted that he executed a go-around during his first approach because visibility had been reduced due to rain on the windshield. At the time of his second approach the shower had passed. He estimated the visibility at 10 statute miles at that time. He reported that he was landing on runway 14 while the Cessna aircraft was landing on runway 35. He stated that neither pilot saw the other aircraft involved, which resulted in a "minor" collision. The Piper's right wing tip contacted the Cessna's right flap and right horizontal stabilizer resulting in substantial damage to the Cessna. The Piper airplane was undamaged in the collision. The Piper aircraft was not equipped with a communications radio. Federal Aviation Administration (FAA) regulations require pilots to "see and avoid" other aircraft when possible. Part 91.119, right-of-way rules, stated that when weather conditions permit "vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft." In addition, "aircraft, while on final approach to land or while landing, have the right-of-way over other aircraft in flight or operation on the surface, except that they shall not take advantage of this rule to force an aircraft off the runway surface which has already landed." The FAA Aeronautical Information Manual (AIM) noted: "There is no substitute for alertness while in the vicinity of an airport. It is essential that pilots be alert and look for other traffic and exchange traffic information when approaching or departing an airport without an operating control tower. This is of particular importance since other aircraft may not have communication capability." According to an airport diagram, the runway intersection was located approximately 1,700 feet from the approach end of runway 35 and approximately 550 feet from the approach end of runway 14. A Cessna T210N airplane sustained substantial damage and a Piper PA-25 airplane was undamaged during an on-ground collision which occurred while both aircraft were landing on intersecting runways. The Cessna pilot reported that he made several position reports on the common traffic advisory frequency (CTAF) for the uncontrolled airport as the flight approached to land. He stated that he entered the traffic pattern and landed on runway 35. He reported that as the aircraft was rolling out after landing he observed the Piper aircraft landing on runway 14 to his immediate left. He noted that the Piper aircraft passed in front of his Cessna. He stated that he applied brakes and "swerved hard to the left," but was unable to avoid a collision. The Cessna pilot reported that his aircraft departed the left side of the pavement "slightly" where it struck a runway light before he regained control. The Piper pilot reported that he was landing on runway 14 while the Cessna aircraft was landing on runway 35. He stated that neither pilot saw the other aircraft involved, which resulted in a "minor" collision. The Piper aircraft was not equipped with a communications radio. Federal Aviation Administration (FAA) regulations require pilots to "see and avoid" other aircraft when possible. Right-of-way rules (14 CFR 91.119) stated that when weather conditions permit "vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft." In addition, aircraft on final approach to land or in the process of landing "have the right-of-way over other aircraft in flight or operating on the surface, except that they shall not take advantage of this rule to force an aircraft off the runway surface which has already landed." The runway intersection was located approximately 1,700 feet from the approach end of runway 35 and approximately 550 feet from the approach end of runway 14. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_CHI05LA128.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 ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…