NTSB CAROL · Event
Event IAD05LA057
Registry · N8251F
FAA Aircraft Registry record.
Make / Model
VAN'S AIRCRAFT RV-7
Year of manufacture
2022
Engine
LYCOMING IO-360-C1C6 (200 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
20230617
ADS-B equipped
Yes — Mode-S AB45EF
Registrant of record
SCHNEIDER RYAN S
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's improper decision to depart with a tailwind, and his failure to perform preflight performance calculations.
Factual narrative
On April 20, 2005, at 1247 eastern daylight time, a Piper PA-28-151, N8251F, was destroyed during a collision with trees and terrain, and a subsequent post crash fire, following a takeoff from Hampton Airfield (7B3), Hampton, New Hampshire. The certificated private pilot/owner and the passenger received serious injuries. Visual meteorological conditions prevailed, and no flight plan was filed for the 14 CFR Part 91 personal flight, destined for North Central State Airport (SFZ), Pawtucket, Rhode Island. During interviews with a Safety Board investigator and a Federal Aviation Administration (FAA) inspector, the pilot described the circumstances surrounding the accident. According to the pilot, they departed from their home base of Pawtucket about 0900 on the day of the accident. During the flight to Hampton, the pilot did not notice any mechanical anomalies. While the pilot and his passenger ate lunch at the airfield, they observed the winds "bouncing back and forth." The winds were "light," but changing directions frequently on the runway. The pilot believed that they seemed to favor runway 02, so he elected to depart from that runway. He did not perform any preflight performance calculations, such as density altitude or takeoff distance. Following a run-up check of the engine, the pilot configured the airplane for a short field takeoff by setting the flaps to "two notches," or 25 degrees. He then accelerated the airplane in a turn onto the turf runway and proceeded to take off. The airplane initially seemed to accelerate normally, but then appeared to "struggle" to reach 45 knots. Once the airplane left the ground, the pilot knew that there was a problem, but was not sure if he could land the airplane with the amount of runway remaining. The pilot did not notice any loss of power during the takeoff, but did feel that the engine "was not running at full power." When asked, the pilot could not recall any indications of the engine power instruments during the takeoff, and did not recall hearing any abnormal engine sounds. During the takeoff he felt that he "just couldn't get the power needed for takeoff," which resulted in the airplane "stalling," and subsequently impacting trees. According to a local police officer, he observed the airplane departing from the airfield. He estimated that the airplane was about 30 feet above the ground, and that it was "teetering" from side to side during the takeoff. As the airplane passed over the officer, he heard a loud "sputtering." He then heard a loud noise as the airplane impacted trees and the ground. The officer moved to a position to where he could better see where the airplane had come to rest, and observed a large amount of thick black smoke, then heard a loud explosion. The officer spoke to the pilot before he was taken to the hospital. The pilot stated that he was attempting to depart from runway 02, but was unable to reach a sufficient airspeed. A witness, who owns a hanger on the east side of the airport, observed the airplane during the takeoff. The witness first noticed the airplane through the door of the hangar, and due to the distance the airplane had traveled down the runway compared to the altitude it had reached, he became concerned. He ran outside of the door and observed the airplane near the tops of the trees on the north side of the runway. Once outside, he felt the wind at his back, and observed that the windsock was pointed "down the runway," blowing in a direction from south to north. The witness also noted that the airplane was never more than about 40 feet above ground level during the takeoff, and described the engine sound as "pulling pretty hard and doing what it was supposed to." The witness further stated that the winds at the airport were often subject to change, and could completely change direction from one hour to the next. He also stated that the airport was equipped with two windsocks at each runway end, and one windsock in the middle of the airport. The wreckage was examined at the scene by an FAA inspector, and was subsequently moved to a recovery facility. The wreckage was then re-examined under the supervision of an FAA inspector on April 27, 2005. According to the inspector, the airframe had largely been consumed by fire. Control continuity was confirmed from the cockpit area to all flight control surfaces. The propeller was separated from the engine, and the spinner exhibited signs of rotational twisting. One propeller blade was bent forward and twisted slightly about 2/3 of its span, and the other blade was curved aft and twisted. Engine continuity was confirmed from the crankshaft flange to the rear engine gears. Both magnetos were fire damaged, and were unable to be rotated. No evidence of pre-impact malfunction or failure of either the engine or airframe was noted. The pilot held a private pilot certificate with ratings for airplane single engine land and sea. He reported during an interview that he had accrued about 400 total hours of flight experience, "most" of which was in the accident airplane make and model. When asked, the pilot stated that he had never operated from Hampton Airfield prior to the day of the accident, and that he had accumulated about 3 to 4 prior hours of experience operating from turf runways. Hampton Airfield was comprised of a single 2,100-foot by 170-foot turf runway. Sixty-foot trees were located 450 feet from the departure end of runway 02. The weather reported at Pease International Tradeport Airport (PSM), Portsmouth, New Hampshire, at 1255, included winds from 250 degrees at 14 knots, gusting to 18 knots, 10 statute miles visibility, scattered clouds at 6,000 feet, broken clouds at 25,000 feet, temperature 84 degrees Fahrenheit, dew point 43 degrees Fahrenheit, and an altimeter setting of 29.67 inches of mercury. According to a recent FAA form 337, the basic empty weight of the airplane was 1507.6 pounds. In a report prepared by the local police department, the combined weight of the pilot and the passenger was 405 pounds. According to the pilot, the airplane's fuel tanks were full prior to his departure from Pawtucket, and prior to departing from Hampton, the fuel tanks contained about 30 gallons of fuel. A review of a Piper Cherokee Warrior Information Manual revealed a chart entitled "Obstacle Clearance Short Field Take Off Distance." According to the chart, assuming a paved, level, and dry runway; the maximum gross weight of 2,325 pounds; full power before brake release; 25 degrees of flaps; a lift-off, and climb speed at the 50 foot obstacle of 52 knots; a pressure altitude of 320 feet; and a temperature of 84 degrees Fahrenheit; the required ground roll would be 1,800 feet, and the distance required to over fly a 50-foot barrier would be 2,200 feet in zero wind conditions. The same previous conditions with a 5-knot headwind would require a 1,600-foot ground roll and 2,000 feet to over fly a 50-foot barrier. A 5-knot tail wind would require a 2,300-foot ground roll, and 2,700 feet to over fly a 50-foot barrier. Prior to departure, the pilot did not perform any preflight performance calculations. Following a run-up check of the engine, he configured the airplane for a short field takeoff, accelerated airplane in a turn onto the turf runway, and proceeded to take off. Once the airplane left the ground, the pilot knew that there was a problem, but was not sure if he could land the airplane with the amount of runway remaining. The airplane subsequently impacted trees during the climb out. During the takeoff, the pilot felt that the engine "was not running at full power," but could not recall any indications of the engine power instruments, nor did he hear any abnormal engine sounds. A witness observed the airplane during the takeoff, and became concerned after seeing the runway distance the airplane had covered, compared to the altitude it had achieved. The witness also noticed the airplane was taking off with a tailwind, with the windsock pointed "down the runway." He described the engine sound as "pulling pretty hard and doing what it was supposed to." A post accident examination of the airplane revealed no evidence of any pre-impact malfunction or failure. Calculation of the takeoff distance, that given the conditions on the day of the accident, and if the airplane were loaded to its maximum gross weight, departing from a paved runway, 2,700 feet was required to clear a 50-foot barrier. The runway was 2,100 feet long, and 60-foot trees were located 450 feet from the departure end. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_IAD05LA057.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- arXiv 2023 · arXiv preprint
Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint
Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint
Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…
- arXiv 2022 · arXiv preprint
Enhanced Prediction of Three-dimensional Finite Iced Wing Separated Flow Near Stall
Icing on three-dimensional wings causes severe flow separation near stall. Standard improved delayed detached eddy simulation (IDDES) is unable to correctly predict the separating reattaching flow due…
- Embry-Riddle Scholarly Commons 2021 · Journal article (JAAER)
Analysis on the Negative Emotional, Physiological, and Cognitive Responses Elicited from of the Activation of a Stall Alarm
Failing to identify an aerodynamic stall can lead to the inability of an aircraft to sustain flight. To warn pilots of an impending or fully-developed stall, many aircraft have safety devices installe…
Browse the full corpus — academia portal ↗