Pilot CAN'T fly WITHOUT GPS/iPad | Calm ATC helps the aircraft land safely (and 02 Lives)

Advertisement

A Mooney M20F operating IFR in the New York area became increasingly difficult for its pilot to control as turbulence, wind and rain disrupted the flight. The aircraft descended below safe minimum vectoring altitude, climbed and then descended again. The pilot became confused by ATC instructions and increasingly dependent on an iPad for navigation, even as its battery was nearly exhausted. Controller Jeffrey Schuler isolated the emergency, redirected the aircraft toward a usable airport and repeatedly brought the pilot's attention back to aircraft control.

Accident Facts

Date
22 December 2015
Registration
N9525M
Timeline
22 December 2015 —
The Mooney M20F N9525M was operating IFR in the New York area.
1.
During the emergency —
The aircraft descended as low as 700 feet, climbed to 1,800 feet and later descended again to 800 feet.
2.
During the approach problem —
The pilot reported difficulty holding altitude and headings in turbulence, wind and rain.
3.
New York TRACON —
Controller Jeffrey Schuler took over the emergency and selected Stewart Airport as an initial landing option.
4.
During the diversion —
The aircraft repeatedly flew opposite to assigned instructions and lost altitude.
5.
After other traffic was moved off the frequency —
Schuler concentrated on N9525M and monitored fuel and the aircraft's performance.
6.
Later —
The pilot reported an engine loss and the aircraft was directed toward Sikorsky Memorial Airport.
7.
During the approach —
The controller became concerned about the low-battery iPad and provided vectors for a VOR approach instead.
8.
At approximately 600 feet AGL —
The aircraft broke out of cloud and completed a circling approach to Runway 29.
9.
Outcome —
The Mooney landed safely.
10.

The aircraft was already below safe margins

NATCA's account records a severe altitude problem before the iPad became the central issue. N9525M descended to 700 feet, climbed to 1,800 feet and then descended to 800 feet near Islip/MacArthur Airport. Two radio towers in the area stood 643 and 821 feet high.

The pilot reported that turbulence, wind and rain made it difficult to hold altitude and headings. Controllers therefore had to manage both navigation and the immediate risk of terrain or obstacle clearance.

The controller simplified the problem

Schuler checked weather and initially chose Stewart Airport because its conditions and runway length offered a more practical landing option. The aircraft did not reliably follow the assigned vectors, however, and at times circled and lost altitude.

Management moved other aircraft to another frequency so Schuler could devote his attention to N9525M. The controller also repeatedly checked the fuel state. When the pilot later reported an engine loss, Schuler directed the aircraft toward Sikorsky Memorial Airport, where a suitable approach could be made.

The failing tablet became a distraction

The pilot was using an iPad as a major navigation reference and reported that its battery was nearly exhausted. The problem was not simply that the battery might reach zero; the pilot was becoming distracted by the device while already struggling to maintain the aircraft's attitude and assigned headings.

Schuler therefore changed the emphasis. Instead of allowing the pilot to continue chasing a failing GPS display, he directed the aircraft toward the airport and supplied vectors for a conventional VOR approach. The pilot eventually broke out of cloud at about 600 feet AGL and completed a circling approach to Runway 29.

The documented finding

“Forget the GPS. Level your wings. Fly the aircraft. Do that first.” — Jeffrey Schuler, as quoted by NATCA

Conclusion

The event's central problem was workload. The pilot was operating in difficult weather, struggling to maintain altitude and headings, and relying on a navigation device that was itself becoming unreliable. Schuler's response was to reduce complexity: isolate the frequency, choose a workable airport, monitor fuel, provide simpler vectors and repeatedly return the pilot's attention to aircraft control. The successful landing followed once the pilot regained enough control to use the runway environment.

Sources

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident