FlightFollowerExperimental aircraft Crashes shortly after takeoff…pilot dead (17 Jun 24)
Experimental Aircraft Crashes Shortly After Takeoff — Pilot Killed
The Van's RV-6A had only been airborne for a few minutes when the engine began to sound wrong.
The airplane had departed Lawrence Municipal Airport in Massachusetts for what was supposed to be a short local flight. The pilot planned to remain in the traffic pattern and practice full-stop landings.
Instead, the aircraft developed an apparent engine problem during the initial climb.
The pilot continued around the pattern.
Then the engine reportedly sputtered and quit.
A short time later, it appeared to restart.
Then it quit again.
The aircraft was now heading toward the Merrimack River.
At about 2:15 p.m. on June 17, 2024, the experimental, amateur-built Van's RV-6A, registration N715PA, crashed into the river near Methuen, Massachusetts. The airplane came to rest inverted in approximately three feet of water. The pilot, the sole occupant, was fatally injured. (NTSB Data)
The final moments were captured in the ATC record.
The controller had already cleared the airplane to land. The pilot acknowledged.
Less than a minute later, he reported that he was having a problem.
The controller responded by clearing him to land on any runway.
Then came the pilot's final transmission:
“Oh, oh.”
There were no further communications.
A helicopter pilot who had just landed at Lawrence Airport subsequently saw the aircraft descending over the Merrimack River and advised the controller that it would not make it back to the airport. The helicopter pilot then located the crash site. (NTSB Data)
The accident is a particularly sobering example of the danger of an intermittent engine problem immediately after takeoff. An engine that sputters, briefly recovers and then loses power can create a dangerous temptation to keep flying in the hope that power will return.
For this accident, however, one point must be made very clearly: the NTSB preliminary report did not determine a probable cause. The investigation material available does establish that witnesses heard the engine sputtering and quitting, but it does not establish exactly why the engine lost power or why the pilot's chosen landing area resulted in the fatal outcome. The investigation therefore needs to be distinguished from later speculation.
A Short Local Flight
N715PA was an experimental, amateur-built Van's RV-6A, a two-seat, single-engine aircraft popular in the homebuilt aviation community.
According to the NTSB's preliminary report, he was planning to practice full-stop landings rather than embark on a long cross-country flight. The airplane was cleared for takeoff from Runway 23 at approximately 2:11 p.m. (NTSB Data)
The weather was favorable.
It was daylight.
Conditions were reported as VMC, with clear skies and visibility of approximately 10 miles. The airport observation shortly before the accident recorded winds from approximately 220 degrees at 10 knots, gusting to 19 knots. (NTSB Data)
Nothing in the available preliminary information indicates that weather was the principal problem.
The critical issue developed after takeoff.
Within minutes, the aircraft was in serious trouble.
The Initial Climb
The RV-6A departed Lawrence's Runway 23.
Radar data showed the airplane climbing to approximately 1,650 feet mean sea level before entering a wide right turn toward the downwind leg of the traffic pattern. (NTSB Data)
That part of the flight was consistent with the pilot's stated intention to remain in the pattern.
The aircraft had enough performance to climb away from the airport.
Several witnesses independently reported hearing abnormal engine sounds.
One witness described hearing the engine operating at full throttle before it abruptly stopped.
The airplane then leveled and turned.
The witness initially thought the pilot might be dealing with a fuel problem—or perhaps conducting a simulated engine-out exercise.
The witness never heard the engine restart during that portion of the flight. (NTSB Data)
Another witness provided investigators with an even more significant observation.
That witness heard the engine sputter and quit before the aircraft had reached normal traffic-pattern altitude.
Then, less than a minute later, the witness heard the engine apparently restart.
It sputtered again.
The aircraft was now flying east toward the Merrimack River.
That testimony became important because it suggested that the aircraft may not have experienced one clean, complete engine failure.
Instead, the engine may have been producing intermittent or unreliable power.
An Engine That Would Not Stay Running
A complete engine failure is frightening, but it also provides the pilot with an immediate and unambiguous problem: the aircraft is now a glider.
If the engine comes back, the pilot may believe there is enough power to continue.
If it quits again, the pilot suddenly has less altitude and fewer options.
The NTSB's preliminary report does not say that the pilot deliberately continued because he believed the engine would recover.
It does, however, document the witness accounts of the engine repeatedly sputtering, stopping and apparently restarting. (NTSB Data)
That sequence is important when reconstructing the accident.
The airplane did not simply leave the airport and immediately disappear.
The aircraft remained airborne long enough to enter the traffic pattern.
It then developed an engine problem while maneuvering at relatively low altitude.
The available altitude was limited.
Every second mattered.
ATC Clears the Airplane to Land
The ATC communication provides one of the clearest pieces of the timeline.
The pilot acknowledged the clearance.
At this point, the flight still appeared manageable from the controller's perspective.
Then, less than a minute later, the pilot reported that he was having a problem.
The controller immediately broadened the landing clearance.
Instead of restricting the pilot to the assigned runway, the controller cleared him to land on any runway. (NTSB Data)
The controller was giving the pilot flexibility.
If the aircraft could reach the airport, the pilot could use whichever runway provided the most favorable option.
But the aircraft was no longer in a normal approach.
The pilot had very little altitude with which to solve it.
The Final Transmission
The pilot's next transmission was brief.
He said:
“Oh, oh.”
That was the final communication from N715PA.
There was no formal declaration of an emergency.
There was no extended explanation of the engine problem.
The radio went silent. (NTSB Data)
The brevity of those final words is striking.
But it is important not to assign emotions or intentions to them that investigators have not established.
They could reflect a sudden loss of engine power.
They could simply have been an immediate reaction to the aircraft's changing situation.
What is known is that the transmission was followed by the loss of communications and the final descent toward the river.
The Helicopter Pilot Sees the Problem
Another aircraft soon became an important part of the accident sequence.
From the airport area, the helicopter pilot observed the RV-6A on the downwind leg.
The helicopter then departed and flew toward the area.
That action was significant because the accident site was not immediately accessible from the nearest roads.
The aircraft had gone down in a difficult section of the Merrimack River, surrounded by dense brush and wooded terrain.
Emergency responders faced access problems as they attempted to reach the wreckage.
The Crash Into the Merrimack River
The RV-6A came down near the boundary of Methuen and North Andover, in the Merrimack River.
There was no post-impact fire. (NTSB Data)
The first responders reached the airplane using boats.
The aircraft's position made access to the cockpit difficult.
According to contemporary local reporting, emergency crews from North Andover, Lawrence and Methuen responded with marine units, while firefighters worked through dense vegetation and difficult river access to reach the wreckage. (Merrimack Valley Stringer)
He had suffered fatal injuries.
There were no passengers.
There were no reported ground injuries.
Why the River Matters
The location of the forced landing is an important part of the accident.
An aircraft experiencing an engine problem immediately after takeoff has to balance several competing considerations.
The pilot needs to maintain adequate airspeed.
He needs to avoid a stall.
And if there is insufficient altitude to return to the departure runway, he must select the safest reachable area ahead or within a shallow turn.
Water introduces another hazard.
A controlled ditching can sometimes be survivable, but an aircraft that ends up inverted in water presents a serious egress problem.
It does, however, establish the aircraft's final sequence and the fact that the airplane came to rest inverted in the water. (NTSB Data)
That distinction is important.
The investigation must determine why the airplane followed the path it did and whether the pilot had any practical alternatives given the altitude, engine performance and surrounding terrain.
The RV-6A
The RV-6 family is widely used by private pilots and builders.
Because the aircraft was amateur-built, its individual configuration can vary depending on the builder's choices, including engine, propeller, fuel-system components, avionics and other equipment.
The NTSB's investigation therefore had to examine the individual aircraft rather than assuming a standardized factory configuration.
The airplane was registered as N715PA.
Records and aviation-community discussion indicate that the aircraft had been completed and received its airworthiness certificate several years before the accident. Contemporary members of the local experimental-aircraft community also reported that the pilot was involved with the local Experimental Aircraft Association community. (Van's Air Force)
Those details provide some context without changing the technical findings.
This was not an airline flight.
It was a local general-aviation flight in a homebuilt aircraft.
The pilot was practicing takeoffs and landings when the emergency developed.
What the NTSB Found at the Scene
After recovery, the airplane was transported to a secure salvage facility for further examination.
The preliminary report states that the aircraft was substantially damaged.
It also confirms that there was no post-impact fire and no evidence of an explosion. (NTSB Data)
One witness reported hearing it apparently restart and then quit again.
Those observations are consistent with an intermittent power problem.
But an eyewitness hearing an engine does not provide enough evidence to determine whether the underlying issue was fuel, ignition, induction, mechanical failure, control-system malfunction or another cause.
The ATC Audio Reveals a Rapidly Developing Emergency
For an ATC-focused reconstruction, the radio sequence is unusually short but highly informative.
“Oh, oh.”
Silence.
The brevity of the exchange demonstrates an important reality of low-altitude emergencies.
A pilot does not necessarily have time to make a detailed radio call.
At 1,500 or 2,000 feet, an engine problem can become a forced-landing decision in seconds.
The priority is maintaining control.
The radio becomes secondary.
The controller therefore had only a limited window in which to understand what was happening.
The pilot had even less time.
The Importance of the First Few Minutes
That is significant because an engine problem during the initial climb presents a very different problem from an engine failure at cruise altitude.
At altitude, a pilot may have several minutes to troubleshoot.
Immediately after takeoff, there may be only seconds.
The airplane may be climbing slowly.
The landing runway may already be behind it.
Turning back requires a certain amount of altitude.
A low-altitude turn can also increase stall risk.
The safest course may therefore be to lower the nose, preserve airspeed and land within the area that can actually be reached.
But those decisions depend on what the engine is doing.
In N715PA's case, the engine reportedly did not behave consistently.
It sputtered.
It quit.
Then it quit again.
That uncertainty may have made the emergency more difficult to manage.
No Evidence Yet of a Single Definitive Failure
It would be tempting to label this accident simply as an "engine failure."
The available evidence supports something more cautious.
Witnesses described repeated power interruptions.
But the NTSB had not yet established the precise mechanical cause in the preliminary report.
That difference matters.
Possible causes of an intermittent loss of power in a piston aircraft can include problems involving fuel delivery, fuel contamination, carburetion or fuel injection, ignition, electrical systems, induction, mechanical components or other systems.
It must also establish whether the engine was producing power at different points in the final flight.
A Difficult Rescue
The crash location created another layer of difficulty.
The Merrimack River in this area is bordered by trees, brush and limited road access.
Contemporary local reporting described firefighters initially struggling to reach the crash site because of dense vegetation.
Responders eventually approached using boats.
The aircraft was inverted on the riverbed, making access to the occupant difficult. (Merrimack Valley Stringer)
For responders, the accident therefore became both an aviation emergency and a water-rescue operation.
The fact that the airplane came down in only a few feet of water did not make the scene straightforward.
The aircraft's inverted position created significant access problems.
The pilot could not be rescued.
The NTSB Probable Cause: Not Yet Established
Therefore, unlike accidents for which a final NTSB report has already established a probable cause, there is no final NTSB probable-cause sentence that can responsibly be quoted here.
Witnesses reported engine trouble.
The pilot transmitted, "oh, oh."
Communications stopped.
The aircraft descended into the Merrimack River.
Anything beyond it should be clearly identified as analysis or hypothesis rather than an NTSB finding.
Accident Facts
- Aircraft
- Van's RV-6A
- Registration
- N715PA
- Aircraft category
- Experimental, amateur-built
- Date
- June 17, 2024
- Time
- Approximately 2:15 p.m. EDT
- Location
- Merrimack River near Methuen, Massachusetts
- Departure
- Lawrence Municipal Airport (LWM)
- Planned flight
- Local traffic pattern
- Runway
- 23
- Occupants
- 1
- Fatalities
- 1
- Survivors
- 0
- Weather
- VMC
- Visibility
- Approximately 10 miles
- Wind
- 220° at 10 knots, gusting 19 knots
- Reported problem
- Engine sputtering / loss of power
- Final landing area
- Merrimack River
- Aircraft position after crash
- Inverted, approximately 3 ft of water
- Post-impact fire
- None
- NTSB accident number
- ERA24FA265
- NTSB report status
- Preliminary; probable cause not established
The FAA's accident summary confirms that the crash occurred on June 17, 2024, and that the NTSB was assigned the investigation. (FAA)
Aviation accident databases independently list the event as the fatal June 17, 2024 crash of RV-6A N715PA near Lawrence/Methuen, Massachusetts. (Rivet Bangers)
What the Accident Teaches About Engine Problems After Takeoff
A pilot who experiences an unreliable engine cannot assume that power will remain available.
If the engine sputters and then recovers, the temptation may be to continue toward the airport.
But intermittent power can disappear again without warning.
The safe response requires maintaining control first.
Airspeed must be protected.
The airplane must remain within a controllable flight envelope.
The accident also illustrates why a return to the departure runway is not automatically the best choice after an engine problem.
The runway may be behind the aircraft.
A turnback may require more altitude than is available.
An off-airport landing may be safer.
The correct decision depends on the aircraft's altitude, position, terrain, engine condition and pilot capability.
In this case, the aircraft ended up over the Merrimack River.
The NTSB has not established whether another landing area was realistically available or whether the pilot's final path was the result of deliberate decision-making, an engine condition, aerodynamic limitations or some combination.
The Human Side of the Accident
The pilot was the sole person aboard.
There were no passengers and no ground victims.
But the loss was still significant to the local aviation community.
Contemporary discussion among pilots at Lawrence described the accident as especially difficult because the aircraft had departed a familiar local airport and the emergency unfolded within minutes. Members of the local EAA community expressed condolences and described the pilot as someone known around the airport. (Van's Air Force)
For a small airport community, these accidents are personal.
The controller's voice is familiar.
And the person flying may be someone other pilots have spoken with only days earlier.
That human connection is worth remembering when reconstructing an accident for an aviation audience.
The Broader Aviation Safety Lesson
The weather was good.
The aircraft climbed normally enough to enter the traffic pattern.
Then the engine began behaving unpredictably.
Then it quit again.
He reported a problem.
“Oh, oh.”
One person died.
The NTSB investigation has not established a final cause, and that uncertainty should be respected. What the available evidence does demonstrate is how quickly an intermittent engine problem can turn a routine traffic-pattern flight into an emergency with almost no altitude to spare. (NTSB Data)
For pilots, the broader lesson is straightforward: after takeoff, unreliable power should be treated as a serious emergency even if the engine appears to recover.
The airplane must remain under control.
And the landing decision must be based on what is reachable—not what is merely desirable.
The accident also demonstrates the value of ATC during a low-altitude emergency. The controller immediately expanded the landing clearance when the pilot reported trouble, while another pilot in the area provided valuable information about the aircraft's final position. (NTSB Data)
But ATC cannot create altitude.
It cannot restart an engine.
And it cannot make an unreachable runway reachable.
Those final decisions belong to the pilot.
At Lawrence, the distance between a normal traffic-pattern flight and a fatal forced landing was measured in minutes.
The final investigation may provide a clearer explanation of what happened inside the engine and why the aircraft ended up over the river.
Until then, the most responsible conclusion is also the most important one: when power becomes unreliable after takeoff, every second counts, and the safest landing site is the one the airplane can actually reach under control.
Primary Source / Investigation Record
Investigation reference: ERA24FA265