ATC Response After a Plane Crashes Into a Golf Course

The event in context

On the night of 9 March 2025, a Beech A23-19 Musketeer Sport III, registration N4784J, was operating near Rochester International Airport in Minnesota. The airplane was conducting local pattern work when its engine lost power during the initial climb. The pilot declared an emergency and attempted a restart before making a forced landing. The aircraft struck trees at Oak Summit Golf Course and sustained substantial damage. The pilot survived with minor injuries.

The NTSB preliminary report identifies the accident as CEN25LA114. It states that the engine experienced a complete loss of power at about 650 feet above ground level. The pilot reported hearing a “click click” immediately before the power loss. The investigation was still preliminary, so the mechanical cause should not be presented as established fact.

The flight was local, which can create a misleading sense of safety. Pattern work keeps an aircraft close to the airport, but an engine failure shortly after takeoff can still leave only seconds to select a landing area.

The NTSB preliminary report for N4784J is unusually precise about the first seconds of the emergency. During the initial climb, at about 650 feet AGL, the Beech A23-19 experienced a complete loss of engine power. The pilot reported that the engine did not sputter and that he heard a ‘click click’ immediately before the power loss. He declared an emergency, attempted a restart and then made a forced landing into trees at Oak Summit Golf Course.

Reconstructing this flight

The pilot’s immediate priorities were appropriate: declare the emergency, attempt an engine restart while altitude permitted, and then transition to the forced-landing plan. The aircraft descended into the golf course rather than attempting an aggressive return to the runway.

That decision matters. A low-altitude turnback can require more altitude than a pilot has available. An off-airport landing may damage the aircraft, but it can be the safer option when the runway cannot be reached without a steep or low-altitude maneuver.

The aircraft was retained for further examination, so the mechanical cause must not be invented. The correct conclusion at this stage is that there was a sudden complete power loss and that the pilot transitioned to a forced landing. The NTSB explicitly states that the preliminary information is subject to change.

What the evidence establishes

That uncertainty is important. Aviation reporting should distinguish between what the pilot experienced and what investigators ultimately prove. An engine can stop because of fuel, ignition, mechanical failure, induction problems or other causes. Without the completed examination, assigning a specific cause would be speculation.

The established safety lesson does not depend on the final mechanical finding. At roughly 650 feet AGL, the pilot had a narrow window to choose between troubleshooting, attempting a restart and selecting a survivable landing area.

The emotional ATC element of this incident comes from the controller’s concern after the aircraft disappeared from the expected pattern and emergency services were needed. For controllers, an aircraft going down near an airport is one of the most stressful situations because the controller has limited ability to know what happened on the ground.

The golf course matters because it became the emergency landing area after the runway was no longer realistically available. The accident therefore provides a concrete departure-path case: the pilot had hundreds of feet rather than thousands, and the outcome depended on choosing an area where the aircraft could descend without attempting a low-altitude turnback that might have been impossible to complete.

Investigation and findings

The incident also shows why local pattern work should be treated as real flight, not casual flying. Engine failure can occur at any time, and every takeoff should include an immediate mental plan for the area ahead.

The Power Loss at About 650 Feet

The reconstructed sequence can be read as a chain of six decision points: Local pattern → Power loss ~650 ft → Mayday + restart attempt → Golf-course forced landing → Tree impact → Pilot survives. Each step changed the aircraft’s available options. The important analytical point is not to isolate the final impact from the preceding events; the final outcome was produced by the accumulation of the earlier changes in aircraft state, position, workload and available escape options.

The ATC/radar perspective is most useful when it is synchronized with the aircraft evidence. In this case the critical transition is the move from local pattern to pilot survives. Once the aircraft reached the later stages of the sequence, the crew had fewer safe alternatives than they had at the beginning. That is the operational value of reconstructing the event rather than describing it only from the final crash scene.

From Mayday to the Golf-Course Landing

The decisive safety issue in this incident was specific to the sequence: Power loss ~650 ft; Mayday + restart attempt; Golf-course forced landing. Treating those events as isolated anomalies would miss the way they interacted.

Sources and investigation material

• https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/199824/pdf

Accident Facts