13 July 2026, Ted Smith Aerostar 601P, N800AA, Lake Clear, New York [Fatal]

On July 13, 2026, about 2236 eastern daylight time, a Smith Aerostar 601P, N800AA was destroyed when it was involved in an accident near Lake Clear, New York. The private pilot and two passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

[Photo: adirondack explorer]

According to preliminary information from the FAA, the airplane was based at Monmouth Executive Airport (BLM), Belmar, New Jersey. Earlier on the night of the accident, the pilot flew uneventfully from BLM to Adirondack Regional Airport (SLK), Saranac Lake, New York. He intended to pick up two family members and return to BLM the same evening. FAA ADS-B data were available for the inbound flight; however, the airplane did not gain enough altitude on the outbound flight for FAA ADS-B data to be recorded.

SLK was located at 1,662 ft above mean sea level (msl) and runway 23 was 6,573 ft-long. Review of third-party commercial surveillance data revealed that the accident flight departed runway 23, at 2235:45. The last target was recorded 46 seconds later, at 2236:31, indicating a location about 1 mile from the departure end of the runway. The data also indicated that the airplane reached a maximum height of about 125 ft above ground level (agl), before descending and leveling off at 75 ft agl for the last five recorded targets, spanning 12 seconds. During that time, the groundspeed increased from 151 knots to 169 knots.

Review of home security video near the accident site revealed an engine sound at 2236, followed by the sound of collision with trees. The wreckage was located about 4 hours later by first responders, and a postimpact fire had consumed a majority of the airplane.

A debris path was observed in a nearby forest, beginning with a section of right wingtip, located about 1-mile beyond the departure end of runway 23. The debris path extended on a 230° magnetic course for about 1/2 mile, to the main wreckage. Severed trees, a section of right flap, and a small section of lower empennage were also located along the debris path.

The wreckage came to rest flat and upright, oriented on a magnetic heading of 180°, at an elevation about 1,668 ft msl.

All major components of the airplane were identified. Both engines were located near the main wreckage and both propellers remained attached to their respective engine. The empennage was located next to the left engine, and sections of both wings were identified near the main wreckage. The cockpit and cabin were consumed by fire.

The pilot held a private pilot certificate with ratings for airplane single engine land, airplane single-engine sea, airplane multiengine land, instrument airplane, and rotorcraft helicopter. He reported a total flight experience of 1,025 hours on an application for an FAA third-class medical certificate, dated December 17, 2025. The pilot obtained an instrument rating on October 3, 2024. At that time, he reported a total flight experience of 890 hours; of which, 102 hours were at night.

The airplane was manufactured in 1976 and powered by two Lycoming IO-540, 290-hp engines, each driving a three-blade Hartzell constant speed propeller. The airplane’s most recent annual inspection was completed on February 2, 2026. At that time, the airframe had accumulated 4,094 total hours of operation. The left engine had accumulated 79 hours since major overhaul (SMOH) and the right engine had accumulated 780 hours SMOH.

Review of FAA Terminal Procedures, takeoff minimums for runway 23 at SLK, revealed instructions to climb 316 ft for every 1 nautical mile traveled, to ensure obstacle clearance, or perform a visual climb over the airport to 2,500 ft msl.

The wreckage was retained for further examination. Additionally, a copy of the home security video was forwarded to the NTSB Vehicle Recorders Laboratory for sound spectrum study.

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

Condolences to the loved ones.

Of course the first thing that comes to mind with these is a mis-handled OEI on takeoff, but that’s pure speculation at this point. I don’t know much about the Aerostar except that it’s very high performance, it has thin wings, and it breaks abruptly in a stall, i.e. low speed maneuvering is very risky. I think it’s very unforgiving of any delay or mistake when handling an engine failure after takeoff.

Again, I’m purely speculating on the cause.

Sadly it appears to have been members of the same family onboard, including an infant. :folded_hands:

2 Likes

The aircraft breaks when it stalls? Thin wings? I guess the fuel tanks must be elsewhere then. An awful tragedy, particularly if it involved a young child, who had no choice in whether or not to board the plane. The pilot seemed well qualified, not that this would necessarily prevent an accident. It’ll be interesting to see what the probable cause of this was.

1 Like

It doesn’t structurally break. The stall “break,” is a colloquialism for its behavior when the wing aerodynamically stalls, meaning that the onset of a stall is very sudden with little buffet/warning before the stall fully develops.

2 Likes

Oh, I see. Thank you for clearing this up. I was thinking it would be a very dangerous plane to stall and it must have something to do with the thin wings. :roll_eyes:

The wings have a very high loading. That doesn’t imply that they’re structurally weak, just that they can be less forgiving. The tradeoff is that they lend themselves to high performance (speed).

1 Like

Nearby surveillance video recorded the sound of two working engines in the moments leading up to the crash.

If there was no mechanical issue then looking at the ADS-B data combined with the nighttime departure and the pilot’s experience level, perhaps this pilot suffered from somatogravic illusion.

@RufusXS what is an OEI please and how would you mishandle it?

One engine inoperative. It’s an urgent situation in typical piston twins that requires a specific set of control inputs, engine configuration, and speed management.

1 Like

@RufusXS Many thanks!