# NTSB ERA19FA049: Lancair Legacy RG, N8448J, Gainesville, GA, November 17, 2018

- Type: NTSB accident investigation
- Classification: Accident · Fatal · Class 2 · Field · Final report
- Date: November 17, 2018, 18:35 local (23:35 UTC)
- Place: Gainesville, GA
- Coordinates: 34.278888, -83.824996
- Nearby events: https://openairdocs.org/map.md?lat=34.2789&lon=-83.8250&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining event: [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240)
- Highest injury: Fatal
- Injuries: 1 fatal, 1 serious
- Status: Completed
- Report: Approved by Office Director
- Investigation class: Class 2
- NTSB office: Eastern Region Aviation
- Parties: Continental Motors, FAA/FSDO
- NTSB case key (mKey): 98650
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA19FA049
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/98650/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=98650
- Page: https://openairdocs.org/ntsb/ERA19FA049

## Probable cause

The pilots’ failure to execute a go-around when the nighttime autopilot-coupled approach became unstable, which resulted in a loss of control and subsequent impact with terrain. Also causal was the flight instructor's inadequate supervision of the pilot and his failure to perform remedial action. Contributing to the accident was the inadvertent application of pressure to the pitch control while the autopilot was engaged, which caused an out-of-trim condition that was not identified by either pilot and resulted in control difficulty when the autopilot was disengaged.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=05634A0), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)
- [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=05634A0), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=05634A0), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Attention/monitoring: monitoring other person](https://openairdocs.org/ntsb-findings/02021535): Personnel issues › Psychological · Instructor/check pilot (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/02021535/cases.md?model=05634A0), [All aircraft, 200 cases](https://openairdocs.org/ntsb-findings/02021535/cases.md)
- [Auto flight system: autopilot trim servo](https://openairdocs.org/ntsb-findings/01022216): Aircraft › Aircraft systems · Unintentional use/operation (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/01022216/cases.md?model=05634A0), [All aircraft, 3 cases](https://openairdocs.org/ntsb-findings/01022216/cases.md)
- [Light condition: dark](https://openairdocs.org/ntsb-findings/03036020): Environmental issues › Conditions/weather/phenomena · Effect on personnel (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/03036020/cases.md?model=05634A0), [All aircraft, 448 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md)
- [Info processing/decision: identification/recognition](https://openairdocs.org/ntsb-findings/02041510): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/02041510/cases.md?model=05634A0), [All aircraft, 559 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md)
- [Info processing/decision: identification/recognition](https://openairdocs.org/ntsb-findings/02041510): Personnel issues › Action/decision · Instructor/check pilot (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/02041510/cases.md?model=05634A0), [All aircraft, 559 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md)
- [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Instructor/check pilot (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=05634A0), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Instructor/check pilot (probable cause); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=05634A0), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-events/240/sequence.md?model=05634A0), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)
- [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Joseph W Blandford LEGACY RG, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=05634A0), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The pilot/owner and flight instructor were returning from a cross-country flight and arrived in the vicinity of the airport after dark in visual meteorological conditions. The flight instructor requested (to the air traffic controller) and was cleared for a practice GPS approach to the runway, which was equipped with precision approach path indicator (PAPI) lighting. Flight data indicated the approach was flown using the autopilot. Just after the airplane passed the final approach fix, the flaps were partially extended, the pitch attitude decreased, and the airplane descended below the glidepath. The autopilot commanded nose up elevator and the airplane returned to slightly above the glidepath where it remained stable for about 16 seconds, before drifting to nearly a full-scale course deviation above the glidepath. The autopilot commanded the elevator to nose down, and the electric pitch trim to near the full nose-down position. The autopilot was then disconnected. Although the autopilot can automatically disengage in the event of a system failure, no failures were observed in the recorded data. Therefore, it was likely that the autopilot was manually disengaged. About 15 seconds later, the flaps were extended to full and then fully retracted. The descent rate increased, and the airplane descended below the glidepath, until the recorded data ended when the airplane was about 0.3 mile from the runway. The airplane then struck trees, crossed over a road, and impacted the left side of a localizer antenna platform before coming to rest in the grass short of the runway. Examination of the wreckage and the recorded flight data did not reveal any preimpact electrical or mechanical anomalies that would have precluded normal operation. The pilot's guide for the autopilot system warned that with the autopilot engaged, a small amount of force on the pitch controls can result in the autopilot automatic trim entering an out-of-trim condition. As the airplane drifted above the glidepath, the autopilot attempted to command nose-down elevator, and the elevator servo met with some resistance, as evidenced by the increase in elevator servo torque, which was sufficient to activate the electric pitch trim. Given that there were no indications of a flight control malfunction, it is likely that one of the pilots was applying pressure to the elevator control in the cockpit, and the autopilot applied elevator trim to counteract that pressure, in its attempt to return to the glidepath. At the time the autopilot was disengaged, the pitch trim was full nose down, which likely resulted in an unexpected increase in the (forward) force the pilot felt on the control stick, making it more difficult to control the airplane. The airplane's nose-down tendency would have increased further when the flaps were subsequently extended to full. This would have resulted in an even greater forward force on the control stick. It is likely that the pilot decided to then retract the flapsfully, due to the increased nose-down force on the control stick. However, the flap retraction resulted in an increased descent rate, and the airplane descended farther below the glidepath. A witness and the flight instructor reported that the airplane rolled inverted before impact. The recorded flight data, which ended when the airplane was on the extended runway centerline about 0.3 mile from the runway and about 50 ft above the runway elevation, did not indicate that the airplane had rolled inverted. The struck trees were also located on the extended runway centerline, about 0.1 mile from the end of the runway. Therefore, it is unlikely that the airplane experienced any significant lateral course deviation or roll, between the end of the recorded data and the struck trees. It is likely that the roll occurred after the airplane struck the trees and before it impacted the localizer antenna platform. The flight instructor had limited memory of the accident flight. He recalled that the pilot/owner was flying the airplane during the approach; however, the investigation was unable to determine which pilot was manipulating the controls at the time of the accident.

## Factual narrative

On the evening after the accident, in response to a request from the airport manager, a contractor flew the GPS approach to runway 23 at GVL. He noted that the Precision Approach Path Indicator (PAPI) lighting system, which provides pilots with visual vertical guidance in relation to the approach path, appeared to be consistent with the GPS approach path that he flew. The two-seat, low-wing, composite, retractable tricycle design airplane was built in 2015. It was equipped with an autopilot and an electric pitch, roll, and yaw trim system. According to a Lancair Owners and Builders Organization Lancair Legacy training manual, deployment of the flaps causes the nose to pitch down, requiring up-elevator trim. It further states that "flight without an operational pitch trim system is difficult." According to the Garmin G3X Pilot's Guide, a section titled "Overpowering Autopilot Servos" reads: In the context of this discussion, "overpowering" refers to any pressure or force applied to the pitch controls when the autopilot is engaged. A small amount of pressure or force on the pitch controls can cause the autopilot automatic trim to run to an out-of-trim condition. Therefore, any application of pressure or force to the controls should be avoided when the autopilot is engaged. Overpowering the autopilot during flight will cause the autopilot's automatic trim to run, resulting in an out-of-trim condition or cause the trim to hit the stop if the action is prolonged. In this case, larger than anticipated control forces are required after the autopilot is disengaged. The pilot's guide also notes that in addition to being disengaged manually, the autopilot can also disengage automatically in the event of a system failure, invalid sensor data, or the inability to compute default autopilot modes. The guide did not indicate that the autopilot would disengage automatically due to excessive control or trim forces. No failures were noted in the recorded data, however the guide did not provide details on which failure conditions are captured by the recording system. ***This report was modified on December 15, 2020. Please see the docket for this accident to view the original report.*** On November 17, 2018, about 1835 eastern standard time, an experimental amateur-built Lancair Legacy RG, N8448J, was substantially damaged when it was involved in an accident in Gainesville, Georgia. The private pilot owner of the airplane was fatally injured, and the flight instructor was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The accident occurred during the third flight of the day. The first flight was local and flown solo by the flight instructor; he performed three takeoffs and landings at Lee Gilmer Memorial Airport (GVL), Gainesville, Georgia. Both pilots flew the airplane on the second flight from GVL to Charleston Executive Airport (JZI), Charleston, South Carolina. The accident occurred on thethird fight, which departed JZI about 1728, and arrived in the vicinity of GVL at 1835, about 1 hour after sunset. As the airplane approached GVL, the flight instructor requested clearance from the air traffic controller for a practice GPS approach to runway 23, which the controller approved. Runway 23 was at an elevation of 1,276.9 ft mean sea level (msl) and equipped with a two-light precision approach path indicator (PAPI), located on the left side. A witness in an airplane waiting to takeoff from runway 23 saw the accident airplane approach the runway. He indicated that he saw the landing lights, which "became dim and they appeared to roll 180 degrees" before the accident. The flight instructor recalled that the pilot was flying the airplane on the approach when the airplane suddenly became inverted. He did not recall any further details. According to flight data recorded by the airplane's primary flight display (PFD), while at an altitude of 3,500 ft msl with the autopilot engaged, the airplane arrived at the initial approach fix from the southeast and turned left onto the inbound course. About 12 seconds before the airplane reached the final approach fix, the autopilot vertical mode changed from altitude hold mode to glidepath mode. Just after the airplane passed the final approach fix at an indicated airspeed of 165 knots, the flaps were extended to 17°. The pitch attitude then changed from 0° to about 9°nose down, the indicated airspeed increased from 165 to 177 knots, and the airplane descended below the glidepath. The autopilot elevator servo began applying torque to the elevator in the nose-up direction, and the airplane then stabilized slightly above the glidepath for about 16 seconds. The pitch attitude then increased slightly, and the airplane drifted above the glidepath, as the autopilot began applying torque to the elevator servo in the nose-down direction. About 2.6 nautical miles from the runway at an altitude of 2,200 ft msl (923 ft above the runway elevation) and an indicated airspeed of 138 knots, the landing gear were lowered and the airplane drifted farther above the glidepath. The elevator servo torque increased, and as a result, the electric pitch trim (controlled by the autopilot, when engaged) increased continuously from a value of 8 units to 67 units in the nose-down direction (which is at or near the full nose down position; it remained at this value until the recording ended), as the elevator servo continued to apply torque in the nose-down direction. The pitch attitude decreased to about 2.5° nose down, however the airplane remained above the glidepath. The course deviation indicator (CDI) increased to nearly the full scale "fly down" indication. The engine power parameter was 42%, where it remained for most of the approach. About 1.6 miles from the runway, at an altitude of 1,900 ft msl (623 ft above the runway) and an indicated airspeed of 127 knots, just as the pitch trim servo reached the value of 67 units, theautopilot was disengaged. About 15 seconds later, the flaps were extended to 40°, remained there for about 5 seconds, and were then fully retracted. As the flaps were retracting, the airplane was descending through the glidepath, the descent rate increased from about 600 ft per minute (fpm) to about 1,200 fpm, and the pitch attitude began to slowly increase from about 2° nose down to 2° nose up. The roll attitude varied between 8° left wing down and 3° right wing down after the flaps were retracted. The engine power was reduced to 32% about 4 seconds before the recorded data ended. The last recorded data point was captured when the airplane was about 0.3 mile from the runway, on the extended runway centerline, at an altitude of 1,323 ft msl (46 ft above the runway). The indicated airspeed was 110 knots, the descent rate was 1,029 fpm, the wings were level, and the pitch attitude was about 2.5° nose up. The CDI indicated full scale "fly up" indication. About 0.1 mile from the runway, while on the extended runway centerline, the airplane struck tree tops that were about the same elevation as the runway (the trees were about 50 ft tall and located in a valley), at the edge of a 4-lane divided highway oriented perpendicular to the runway. The airplane descended and impacted terrain and a wooden platform that held the localizer antenna for runway 05, located about 500 ft from the approach end of runway 23. A review of the PFD flight data for each flight on the day of the accident did not reveal any indications of preflight checks of the elevator trim or autopilot system. The Hall County Coroner's Office, Gainesville, Georgia conducted an autopsy on the pilot. The cause of death was generalized trauma. Toxicology testing performed on the pilot by the FAA Forensic Sciences Laboratory identified Alfluzosin and Ibuprofen in urine. Alfluzosin is a prescription medication used to treat symptoms of an enlarged prostate and is not considered impairing. Ibuprofen is an over-the-counter medication used to reduce fever and to relieve minor aches and pain; it is also not considered impairing. According to U.S. Naval Observatory records, the sun had set at 1730, civil twilight ended at 1757, and the moon was in the waxing gibbous phase with 70% of the moons disk illuminated. Examination of the pilot's logbook revealed the last entry was dated August 21, 2017, before he purchased the accident airplane. The logbook contained complex and high-performance endorsements. His experience in the accident airplane was documented in an airplane usage logbook and an email printout; both were found in the wreckage. The records indicated that he flew with another pilot for at least 92 of the 96 flight hours in the accident airplane but did not indicate the nature of those flights or details to document currency. A further review of the PFD flight data revealed that the previous four landing approaches were flown with the autopilot off. Similar to the accident flight, eachapproach was flown using the flaps in two steps, initially about 15-20°, and subsequently 35-40° before landing. During all four approaches, the initial flap deployment occurred at airspeeds that were slower than when deployed on the accident flight by 5 to 25 knots. At the time of initial flap deployments, the airplane's pitch attitude decreased between 1° and 3° on three of the approaches and did not change appreciably on one approach. The final flap selections were made at speeds similar to the accident approach. At the time of the flap movement, the airplane's pitch attitude decreased by 5° to 6° during three of the approaches, and by 3° to 4° degrees on one approach. The recorded values for pitch trim during all the previous landings ranged from a low of -12 (nose up) units to a high of +22 (nose down) units. A review of all recorded data (a total of 10 previous flights dating back to October 7, 2018), revealed limited use, for short durations, of the autopilot during flight. There were no flights, other than the accident flight, in which the autopilot was used during an approach to landing. A 175-ft-long debris path extended from the localizer platform along a heading of 215° magnetic to the main wreckage which came to rest upright, on a heading of about 225°. Additional debris were found near the struck trees on the approach path. Paint chips and small carbon fiber pieces were found at the base of the tree line. The left wingtip and one of the landing gear doors were found in the highway median. Tree branches and limbs were strewn from the tree line across the highway along the runway heading. Examination of the wreckage revealed that all major components of the airplane were present at the accident site. The left wing was fractured and partially separated about 2 ft from the root, and the flap was completely separated from the wing. The right wing was fractured and partially separated at the root, and the right aileron and about 4 ft of the outboard section of the right wing were separated from the wing. The vertical stabilizer was fractured in several locations. An outboard section of the left elevator about 1-ft-long was separated from the remainder of the elevator. The elevator trim tab was deflected trailing edge upward (airplane nose down). The aileron trim tab, located on the left aileron, was faired. The left flap was separated from the wing. The right flap was found in the retracted position. All of the circuit breakers were in (inactivated) with the exception of the 3 amp starter relay breaker, which was in the out (activated) position. The rudder controls were intact and continuous from the pedals to the rudder. The aileron controls were continuous from the control stick through several bending overload breaks in the push-pull tubes, to the aileron control horns. The elevator controls were continuous from the control stick through an overload fracture in the aft push-pull tube rod end. The elevator trim tab was found deflected30°-35° trailing edge up relative to the elevator, which correlated to the airplane nose down direction. Examination of the elevator trim tab servo motor revealed that the actuator arm was nearly in the full nose-down trim position. The motor functioned normally when electrical power was applied in both the nose-up and nose-down directions. Examination of the pitch trim switches on each of the control sticks (pilot side and copilot side) revealed that they functioned normally. The autopilot elevator servo motor rotated freely in both directions when manually rotated. The engine remained attached to the airframe and the propeller remained attached to the crankshaft propeller flange. Chordwise scratches were present on all 3 propeller blades. There were leading edge gouges and aft bending with slight twisting on two blades. The top spark plugs were removed and exhibited light-colored combustion deposits. The spark plug electrodes exhibited normal-to-worn out signatures when compared to the Champion Check-A-Plug chart. The fuel pump remained attached to the engine, the drive coupling was intact, and the fuel pump discharged a small amount of fuel when turned by hand. The fuel nozzles were removed and found to be free of obstruction. The engine crankshaft was rotated by hand using the propeller. The magnetos produced spark on all six top ignition leads. Thumb compression and suction was noted on all six cylinders with proper valve movement established. Continuity throughout the engine and accessory section was established and no anomalies were noted with the engine that would have precluded normal operation prior to the accident.

## Aircraft

- Registration: [N8448J](https://openairdocs.org/deregistered/N8448J-2022-02-05), registration cancelled 2022-02-05, S/N L2K-338, built 2015 (OpenAirDocs)
- Reported make and model: Lancair LEGACY RG (No Series)
- Registry model: [Joseph W Blandford LEGACY RG](https://openairdocs.org/model/joseph-w-blandford-legacy-rg) (registry code 05634A0) (OpenAirDocs)
- Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs)
- Category: Airplane, amateur-built
- Serial number: L2K-338
- Year built: 2015
- Airframe hours: 358
- Engines: Continental Motors IO-550-N8B 310 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Airworthiness certificate: Special, Experimental (Special)
- Last inspection: Condition, December 3, 2017, 149 hours before
- Departed: JZI, Charleston, SC
- Destination: GVL, Gainesville, GA
- Airport: GVL, Lee Gilmer Memorial, runway 23, 5,500 × 100 ft, asphalt
- Equipment: ADS-B, Auto-pilot, Data recorder, Electronic primary flight display, Electronic multifunction display

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 68; injuries: fatal; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: left; restraint: 4-point; toxicology performed; flight hours: 289 total, 96 in this make and model
- Flight instructor; age 69; injuries: serious; flight instructor, airline transport; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; seat: right; restraint: 4-point; flight hours: 7,500 total, 52 in this make and model

## Weather

- Conditions: Visual (VMC), Night
- Wind: 130° at 3 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 52 °F, dew point 39 °F
- Altimeter: 30.20 inHg
- Observed at: GVL

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20181117022629A](https://openairdocs.org/incident/20181117022629A), Nov 17, 2018: Joseph W Blandford LEGACY RG, Gainsville, GA, Destroyed, 1 fatal. Pilots were returning from a day of flying to the carolinas to check on owners boat. Flight back to Gainsville, GA was uneventful and all systems were normal.…

## Docket (22 files)

The files NTSB released with the investigation on October 9, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=98650. 179 MB in all.

- Revisions to factual report (tracked changes) (item 1, PDF, 7 pages, 177 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11706786&FileExtension=pdf&FileName=ERA19FA049_Factual_Repost-Rel.pdf
- Witness statement (item 2, PDF, 1 page, 118 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9631337&FileExtension=pdf&FileName=01-01%20MFR%20Witness%20McGlamry-Rel.pdf
- Record of conversation - surviving pilot (item 3, PDF, 1 page, 137 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9631889&FileExtension=pdf&FileName=01-02%20record%20of%20conversation%20Mark%20Lewis%20Pilot%20Rated%20Passenger-Rel.pdf
- Record of conversation - FAA inspector (item 4, PDF, 1 page, 137 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9630349&FileExtension=pdf&FileName=01-03%20MFR%20FAA%20Inspector_Redacted-Rel.pdf
- Record of conversation - friend of pilot (item 5, PDF, 1 page, 136 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9631831&FileExtension=pdf&FileName=01-03%20MFR%20Russell%20Reel_Redacted-Rel.pdf
- Record of conversation - pilot/owner's wife (item 6, PDF, 2 pages, 190 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9724570&FileExtension=pdf&FileName=01-03b%20MFR%20Conversation%20with%20Theresa%20Alberhasky_v3-Rel.pdf
- Identification of voice in radio transmissions (item 7, PDF, 1 page, 195 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11709073&FileExtension=pdf&FileName=01-04%20MFR%20-%20Identification%20of%20voice%20in%20radio%20transmissions-Rel.pdf
- Record of conversation - contractor - evaluation of runway 23 PAPI lighting (item 8, PDF, 1 page, 140 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9631389&FileExtension=pdf&FileName=01-04%20MFR%20Precision%20Approach%20-%20Evaluation%20of%20Runway%20PAPI%20lighting_Redacted-Rel.pdf
- Excerpts from pilot logbook and aircraft log (item 9, PDF, 16 pages, 5.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9631256&FileExtension=pdf&FileName=02-01%20pilot_log_ac_usage_red_Redacted_red-Rel.pdf
- Pilot flight time tabulation (item 10, PDF, 2 pages, 69 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9632002&FileExtension=pdf&FileName=02-02%20Flight%20Times%20tabulation-Rel.pdf
- Excerpts from garmin pilot guide and Lancair legacy training manual (item 11, PDF, 6 pages, 666 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9632090&FileExtension=pdf&FileName=03-01%20Excerpts%20from%20Garmin%20Pilot%20Guide%20and%20Lancair%20Training%20Manual-Rel.pdf
- Excerpts from maintenance logbook (item 12, PDF, 14 pages, 3.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9631931&FileExtension=pdf&FileName=03-03%20mx_logs._red_Redacted_red-Rel.pdf
- Photo array (item 13, PDF, 4 pages, 4 photos, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9632108&FileExtension=pdf&FileName=06-01-%20photo%20array_19FA049-Rel.pdf
- Engine manufacturer's examination report (item 14, PDF, 7 pages, 12 photos, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9631873&FileExtension=pdf&FileName=06-02%20-Continental%20Motors%20Engine%20Examination%20Report_Redacted-Rel.pdf
- Examination of trim switches and elevator trim tab servo motor (item 15, PDF, 8 pages, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9676584&FileExtension=pdf&FileName=06-03%20Examination%20of%20Trim%20Switches%20and%20Trim%20Tab%20Servo-%20ERA19FA049-Rel.pdf
- Toxicological report (item 16, PDF, 1 page, 107 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9632244&FileExtension=pdf&FileName=07-01%20Toxicology_c_Redacted-Rel.pdf
- Cockpit display - data download factual report (item 17, PDF, 2 pages, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9632117&FileExtension=pdf&FileName=08-01%20Cockpit%20Display%20Download%20Factual%20Report-Rel.pdf
- Plots of flight data - accident flight (item 18, PDF, 12 pages, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9677831&FileExtension=pdf&FileName=08-03%20Plots%20of%20Flight%20Data%20-%20Accident%20Flight-Rel.pdf
- Review of flight data - previous approaches (item 19, PDF, 1 page, 107 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9678103&FileExtension=pdf&FileName=08-04%20Review%20of%20Flight%20Data%20-%20Previous%20Approaches%20Review-Rel.pdf
- Cockpit display - data download - tabular data (item 20, CSV, 160 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9632410&FileExtension=csv&FileName=08-02%20Garmin%20G3X%20tabular%20data%20file_fdr_19990822_000032-Rel.csv
- Statement of party representatives to NTSB investigation (item 21, PDF, 14 pages, 302 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9678505&FileExtension=pdf&FileName=09-01%20Party%20Form%20CMI_Redacted_b-Rel.pdf
- Release of aircraft wreckage, NTSB form 6120.15 and evidence control (item 22, PDF, 11 pages, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9717654&FileExtension=pdf&FileName=09-02%20NTSB%20Wreckage%20Release%20-%20Evidence_Control-ERA19FA049_Redacted-Rel.pdf

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.