Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

June 6, 2019 · Avid AVID Magnum No Series · N3062B

Frederick, MD

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 6, 2019
Injury Outcomes
2 injuries (2 minor injuries)
Location
Frederick, MD
Aircraft
Avid AVID Magnum No Series (2002)
Tail Number
N3062B
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA19LA187

The pilot was receiving instruction in his newly purchased experimental amateur-built airplane to meet insurance requirements. The instructor with whom he was flying had no experience in the accident airplane make/model before the day of the accident. While departing on the second flight of the day, the pilot applied engine power for takeoff. The instructor recalled that the initial takeoff roll was normal. As the tail lifted off and the pilot advanced the throttle fully forward, the airplane swerved toward the left. The pilot applied right rudder; the airplane corrected to the right but continued toward the right uncontrollably. The pilot pushed on the throttle and attempted to initiate a climb. As the airplane crossed over the right edge of the runway, it was “barely airborne,” and the pilot attempted to avoid construction equipment ahead; however, the controls were “mushy” and the airplane “would not respond properly to control inputs.” The tailwheel struck the construction equipment, the airplane nosed over, impacted a small hill, and sustained substantial damage to the right wing, rudder, and vertical stabilizer. Examination of the airplane found no mechanical failures or malfunctions with the airplane that would have precluded normal operation before the accident. Due to the pilot’s unfamiliarity with the vernier-type throttle control, he was unsure if he had advanced the throttle fully forward at the start of the takeoff roll. However, if he had not pushed the throttle to its maximum, that alone should not have affected his ability to control the airplane laterally during the takeoff roll. If the throttle was not fully forward, and the pilot had maintained directional control, the airplane likely would have lifted off normally after an increased ground roll. Based on the instructor’s description of the “mushy” and unresponsive controls at that time and the witness’ description of the airplane appearing to be in “steep climb” as it lifted off, the airplane was likely at or near its minimum controllable airspeed and at a relatively high pitch attitude when it departed the runway. The pilot’s lack of experience with the airplane and his decision to obtain training from an instructor who was also unfamiliar with the airplane likely contributed to the accident.

NTSB Probable Cause

The pilot’s loss of directional control during the takeoff roll, which resulted in a runway excursion. Contributing to the accident was the pilot’s and instructor’s lack of experience in the make and model of the airplane.

Full Narrative

On June 06, 2019, about 1602 eastern daylight time, an experimental amateur-built Avid Magnum, N3062B, was substantially damaged when it was involved in an accident near Frederick, Maryland. The pilot and flight instructor sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The pilot reported that he had recently purchased the airplane. He arranged to fly the airplane with the seller for 2 hours on the day before the accident, and with a flight instructor for 5 hours on the day of the accident to meet his insurance company’s requirements of 5 total hours of dual instruction. During the time he flew with the seller, he did not perform any takeoffs or landings. On the day of the accident, the pilot met the instructor, who did not have any previous experience in the airplane make/model. They “went over” the airplane, practiced maneuvers, takeoffs, and landings, then stopped for lunch and to refuel the airplane. While departing on the subsequent flight, the pilot began the takeoff roll on runway 30 using full power. The airplane made a “small swerve to the left,” which he initially corrected to the right; however, the airplane continued to turn right uncontrollably. He said that he could move the rudder pedal, but it had no apparent effect. He advised that his training had emphasized that he should respond to directional control problems on takeoff roll (in tailwheel airplanes) by “getting the airplane into the air, if possible.” As the airplane veered right, he pushed on the throttle and pulled back to lift off; however, the airplane would not climb and continued to veer to the right, then impacted construction equipment and a small hill. According to the instructor, the takeoff roll was normal until just after the tailwheel lifted off, when the airplane “swerved left and then hard back to the right.” He then “grabbed the stick” and yelled, “power power power” because it seemed to him that the engine was not developing full power based on its sound and the airplane’s performance. As the airplane crossed over the right edge of the runway, it was “barely airborne” until the ground sloped downward about 6 to 8 ft beneath the airplane. He struggled to keep the wings level and believed the airplane was at or near its stall speed. He attempted to avoid the construction equipment; however, the controls were “mushy” and the airplane “would not respond properly to control inputs.” He did not have time to look at the instruments. The instructor believed that the engine should have “had plenty of power to fly us out of the pre-accident situation if it had been developing full power.” In a subsequent statement, the pilot reported that he likely had not advanced the throttle to full power at the start of the takeoff, or when he attempted to lift off as the airplane departed the runway, due to his lack of familiarity with the style of throttle control. The throttle control was a vernier-style and was equipped with a button on the end of the knob. To push the throttle forward, the button needed to be depressed. Like a typical mixture control, the throttle position could be finetuned by rotating the knob. Neither the pilot nor the instructor reported observing the engine tachometer or airspeed indicator at the start of the takeoff roll or at the time of liftoff. According to a witness located at the nearby construction project, the airplane “took off in a steep climb, making small corrections in bank, getting bigger as they went.” An examination of the wreckage by a Federal Aviation Administration inspector revealed that the airplane came to rest inverted against a hill of construction dirt located about 1,400 ft from the departure end of runway 30, and about 400 ft right of the runway centerline. The wings, fuselage, rudder, and vertical stabilizer were substantially damaged. A follow-up examination of the airplane confirmed flight control continuity from all flight control surfaces to the cockpit and revealed no pre-accident anomalies with the engine that would have precluded normal operation. The engine tachometer was marked with a blue range between 2,200 and 2,700 rpm, and a red range above 2,700 rpm. At the time of the accident, the pilot had accrued a total of 715 hours of flight experience, 5 hours of which were in the accident airplane make/model (3 hours were accumulated on the day of the accident). The instructor had accrued a total of 6,030 hours of flight experience, 3 hours of which were in the accident airplane make/model. At 1547, the weather conditions at the accident airport included temperature 31°C, dewpoint 18°C, wind from 330° at 4 knots, altimeter setting 29.82 inches of mercury. The calculated density altitude was 2,384 ft.

Flight

Event TypeAccident
Event Time16:02 EDT
Nearest AirportFrederick Muni (0nm NNE)
Runway30
Runway Length3600 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftAvid AVID Magnum No Series
Tail NumberN3062B
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-A2B · Reciprocating · 150
Seats2

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 68 · Third Class · Minor
Crew 2Age 76 · Second Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind330° @ 4 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point64 F
Altimeter29.81 inHg
Observation Time19:47
Weather SourceWFAC

Appendix: Source Data