FTW96LA287
1996-07-02 · STILLWATER, Oklahoma, United States · None · 1 aircraft · Status: Completed
Airport SWO
Aircraft involved
Probable cause & findings
the failure of the pilots of the Cessna 421B, N450SU, and the Cessna 152, N94532, to maintain visual lookout. Factors were: the inadequate radio communications maintained by both pilots, and the failure of the student pilot of the Cessna 152 to take evasive action.
Factual narrative
On July 2, 1996, at 1045 central daylight time, a Cessna 421B, N450SU, collided with a Cessna 152, N94532, while landing near Stillwater, Oklahoma. Both airplanes were substantially damaged. The commercial pilot and the passenger on the Cessna 421B were not injured. Likewise, the solo student pilot in the Cessna 152 was uninjured. Both airplanes were being operated by the Oklahoma State University of Stillwater, Oklahoma, under Title 14 CFR Part 91. Visual meteorological conditions prevailed and a flight plan had not been filed for the flights by either aircraft. According to personnel at the Stillwater Municipal Airport, the Cessna 421B executed an straight-in visual approach to runway 17 upon return from a local maintenance test flight to check the pressurization system. The Cessna 152, being flown by a student pilot on his second supervised solo flight, was on closed traffic for runway 22. The two airplanes collided at the intersection of runways 17 and 22. According to engineering drawings for the Stillwater Airport, the distance from the landing threshold of runway 17 to the collision point is 3,650 feet. Likewise, the distance from the landing threshold of runway 22 to the collision point is 3,400 feet. A witness at the airport observed the collision. He stated that the Cessna 152 maintained a high rate of speed during the landing roll on runway 22. The airplane "stayed on the runway centerline during most of the rollout, beginning to veer to the right as it approached the intersection." He reported that he also observed the Cessna 421 applying heavy breaking and veering to his right to avoid the Cessna 152. The Cessna 152 pilot stated in the enclosed NTSB Form 6120.1/2 that he was in the pattern for runway 17 and he changed over to runway 22 because the winds were "down the runway for 22." The student pilot further stated that he announced his intentions on the Unicom frequency and he never heard any other traffic announcing their intentions to land at the Stillwater Airport. The added that he never saw the Cessna 421 until just before the collision. The Cessna 421 pilot stated in the enclosed NTSB Form 6120.1/2 that the winds were from 170 degrees at 3 knots and he executed his approach to runway 17. He added that while on final approach he made two calls on the Unicom, one at 3 miles, and another at 2 miles. He added that the Cessna 152 landed long, approximately 1,800 feet from the landing threshold, about 5 to 10 seconds after he landed on runway 17. The Stillwater Municipal Airport is an uncontrolled airport with Unicom service, which was reported to be operational at the time of the accident. Both airplanes were equipped with operational 2-way radios. A flight instructor operating near the Stillwater Airport at the time of the collision heard the radio calls and confirmed that both pilots made the radio calls as they stated. Examination of the airplanes revealed that the left wing tip tank on the Cessna 421 was punctured when it impacted the fully deployed right flap on the Cessna 152. Additionally, right engine propeller damaged the right wing and aileron for the Cessna 152. The blades on the left propeller displayed rotational gouging and scratching consistent with impact with the wing; however, the right propeller on the Cessna 421 was found in the feathered position. The pilot of the Cessna 421B, N450SU, was making a full stop landing on runway 17. The Cessna 152, N94532, flown by a student pilot on his second supervised solo, had landed on runway 22. During their respective landing rolls, the two airplanes collided at the intersection of runways 17 and 22. The uncontrolled airport was equipped with Unicom service, which was reported to be operational at the time of the accident. Both airplanes were equipped with operational 2-way radios, and both pilots stated that they announced their intentions prior to landing. A witness at the airport observed the collision. He stated that the Cessna 152 landed long and maintained a high rate of speed during the landing roll on runway 22. The Cessna 152 stayed on the runway centerline, and began to veer to the right as it approached the intersection. He also reported that he observed the Cessna 421 applying heavy braking, as he tried to veer to the right to avoid the Cessna 152. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_FTW96LA287.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 (maintenance). All research papers
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA) From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2026 · Article (Reliability Engineering & System Safety) Understanding human error in military aviation maintenance: The role of Performance shaping factors, cognitive workload and error orientation
- Semantic Scholar 2025 · Article (Applied Sciences) Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Semantic Scholar 2024 · Article (Defence Science Journal) Modelling of Human Factors in Aviation Maintenance Using HFACS ME Human Factors Analysis and Classification System Maintenance Extension and Bayesian Network
Aircraft maintenance is a complex task involving a skilled human workforce, spare parts, and various other resources. Human factors are an inherent element of the human workforce.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER) A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER) Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…