Velocity V-Twin Crashes Into House Near Nashua Airport

The event in context

On 17 December 2025, an experimental amateur-built Velocity V-Twin, N22EU, was flying touch-and-go patterns at Nashua-Boire Field in New Hampshire. The sole occupant, the pilot, was on his third circuit of the pattern. Coming off a touch-and-go on runway 14, the aircraft made a sharp left turn — and from there, things went wrong quickly.

The aircraft lost altitude in the turn and couldn't recover it. It struck the roof of a house in a residential area near Cannongate Road, then came to rest on the roadway below. The impact destroyed the aircraft. The pilot reportedly got himself out of the wreckage — self-extricated, in the language of the preliminary report — with only minor injuries. No one on the ground was hurt, a genuinely fortunate outcome given the aircraft came down directly into an occupied residential neighborhood.

The NTSB preliminary report ERA26LA070 provides the key physical sequence. On December 17, 2025, Velocity V-Twin N22EU was on its third traffic-pattern circuit at Nashua. While turning toward downwind after a touch-and-go, the airplane steepened its bank and nosed down. The pilot reported applying propeller, mixture and throttle controls fully forward without arresting the descent.

Reconstructing this flight

The Velocity V-Twin is an experimental canard-design aircraft — a pusher-configuration twin with the horizontal stabilizing surface mounted at the front of the aircraft rather than the tail, a layout that flies differently from the conventional trainers most pilots learn on. Canard designs generally have favorable stall characteristics by design, which makes a sudden, unrecovered loss of altitude in a turn like this one particularly worth understanding — it doesn't fit the typical stall-spin pattern these aircraft are built to resist.

The NTSB's preliminary report documents the pilot's account and the physical damage, but a final probable-cause determination hasn't been issued. Investigators retained non-volatile memory cards from the aircraft's avionics for examination, which may help establish exactly what the aircraft was doing — airspeed, bank angle, control inputs — in the moments before it struck the house. Pattern work close to a busy general-aviation airport leaves very little altitude to recover from an unexpected departure from controlled flight, and that thin margin is exactly what turned a routine third circuit into a crash landing in someone's backyard.

NTSB preliminary; avionics data retained for examination, final cause pending.

The airplane struck a house and vehicle and came to rest inverted. The pilot sustained minor injuries. FAA inspectors found substantial damage, while non-volatile memory cards from the avionics were retained for further examination. No pre-impact mechanical malfunction capable of preventing normal operation was reported by the pilot.

What the evidence establishes

Because the investigation is preliminary, the final cause should remain open. The strongest evidence at this stage is the sudden change in bank and pitch during a low-altitude pattern maneuver, followed by an unrecovered descent. The recovered avionics memory may provide the most useful evidence for determining airspeed, attitude and aircraft response in the final seconds.

The Low-Altitude Recovery Attempt

The reconstructed sequence can be read as a chain of six decision points: Third pattern circuit → Touch-and-go → Steep bank + nose-down → Low-altitude recovery attempt → House/vehicle impact → Pilot self-extricates. 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 third pattern circuit to pilot self-extricates. 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.

The Steep-Bank and Recovery Sequence

The decisive safety issue in this incident was specific to the sequence: Touch-and-go; Steep bank + nose-down; Low-altitude recovery attempt. 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/202392/pdf
• https://www.ntsb.gov/
• https://www.aero-news.net/index.cfm?do=main.textpost&id=440AEEF9-76D8-4C68-8D0E-2D2EF46687ED

Accident Facts