Skip to content

Atlas / NTSB / WPR12CA232

NTSB CAROL · Event

Event WPR12CA232

2012-05-27 Page, Arizona, United States Airport · PGA None 1 aircraft Status: Completed

Registry · N21718

FAA Aircraft Registry record.

Make / Model

CESSNA 172S

Year of manufacture

2004 · 8 years old at event

Engine

LYCOMING IO-360-L2A (180 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

20040513

ADS-B equipped

Yes — Mode-S A1D61F

Registrant of record

BLOMGREN DAVID

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's failure to maintain directional control during the landing flare.

Factual narrative

The private pilot was at the airplane controls during the landing approach. Another private pilot was present, and acting in the capacity of a safety/lookout. The pilot held the airplane in a yaw during the landing approach, while the safety pilot looked through the rear window in order to monitor another airplane, which was just behind them. The safety pilot became concerned that the airplane behind was flying too close, and watched as it overflew their position during the flare. He then looked forward and noticed that the airplane was still in a yaw condition, and not aligned with the runway centerline. The pilot attempted to correct the yaw during the flare, but landed in a side load condition on the left main landing gear, and the airplane subsequently veered off the runway. The safety pilot attempted to take control of the airplane, but it continued into the ramp area and collided with two parked aircraft. The airplane and one of the parked aircraft sustained substantial damage during the accident sequence. The pilots reported no preimpact mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation. The private pilot was flying the airplane and another pilot was acting as a safety pilot during the approach to landing. The flying pilot stated that he held the airplane in a left yaw during the final approach, and the safety pilot stated that he was looking through the airplane’s rear window at the airplane that was just behind them. The safety pilot said that he became concerned that the airplane behind them was flying too close and that he continued to watch as it overflew their position during the flare. When the safety pilot looked forward, he noticed that the airplane he was in was in a yaw condition, and the pilot had not aligned the airplane with the runway centerline for landing. The pilot attempted to correct the yaw during the flare, but the airplane landed in a side load condition on the left main landing gear and then veered off the left side of the runway. The safety pilot tried to take control of the airplane, but it continued into the ramp area and collided with two parked aircraft. The accident airplane sustained substantial damage to the left wing and the left side of the main cabin, and one of the parked airplanes sustained substantial damage to its rear cabin and tail section. The accident pilots reported no preimpact mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C

Verbatim from NTSB's published report. Source file NTSB_2012_WPR12CA232.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.