# NTSB ERA22FA227: Schweizer SGS 2-33A, N17879, Blairstown, NJ, May 15, 2022 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Final report - Date: May 15, 2022, 14:58 local (18:58 UTC) - Place: Blairstown, NJ · fenced in field. GPS location - Coordinates: 40.97265, -74.99199 - Nearby events: https://openairdocs.org/map.md?lat=40.9727&lon=-74.9920&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 105076 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA22FA227 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/105076/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=105076 - Page: https://openairdocs.org/ntsb/ERA22FA227 ## Probable cause The student pilot’s failure to maintain proper alignment with the landing area during the approach, which resulted in the left wing impacting a tree. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Decision related to condition (probable cause); cases with it: [Schweizer SGS 2-33A, 4 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=8051606), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Schweizer SGS 2-33A, 13 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=8051606), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: lateral/bank control](https://openairdocs.org/ntsb-findings/01062023): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Schweizer SGS 2-33A, 3 cases](https://openairdocs.org/ntsb-findings/01062023/cases.md?model=8051606), [All aircraft, 390 cases](https://openairdocs.org/ntsb-findings/01062023/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: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Schweizer SGS 2-33A, 7 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=8051606), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis The student pilot was maneuvering the glider for landing in the grass area left of and parallel to the runway after a solo traffic pattern flight. Witnesses reported that, as the pilot turned the glider left from the base leg to final, the turn was “early,” resulting in the glider being left of the approach path, and “slightly higher than normal.” The pilot performed a forward slip and recovered, which appeared to put the glider closer to a normal glidepath; however, it was “somewhat close” to tall trees located to the left of the approach path. The pilot then entered another forward slip, and the glider maintained a slight left bank during the recovery, which placed it closer to the trees. The left wing subsequently impacted a tree and the glider rotated to the left, pitched downward, and descended into a grass field adjacent to the tree line. Examination of the glider revealed no anomalies that would have precluded normal operation. Although a bird remnant was found in the debris path, no remnants were found on the glider or any of its components, and it is likely that the remnant was present before the accident. It is likely that the pilot became fixated on attaining the proper glide path during the landing approach and failed to correct the glider’s lateral misalignment with the intended landing area, which resulted in impact with the tree. ## Factual narrative On May 15, 2022, at 1458 eastern daylight time, a Schweizer SGS-2-33A glider, N17879, was substantially damaged when it was involved in an accident near Blairstown, New Jersey. The student pilot was fatally injured. The glider was operated as a Title 14 Code of Federal Regulations Part 91 solo instructional flight. According to the pilot’s flight instructor, he met the pilot at the airport to review his logbook and plan for two instructional flights. He reported the weather as “good with light winds and smooth conditions” based on flights he performed earlier that day. The two dual flights, which were performed in the traffic pattern for runway 25, were uneventful. The instructor noted that the pilot flew well on each flight, exercised good judgement, and flew well within safety limits. Following the completion of the second flight, the instructor issued a 90-day solo endorsement. It was the pilot’s second 90-day solo endorsement; he had received his first in November 2021. The pilot then flew two solo left traffic pattern flights. The first flight was uneventful. During the 2nd solo traffic pattern flight, the flight instructor noticed that the turn from base to final “looked early, and slightly higher than normal.” The glider then entered a forward slip and descended closer to a “normal glide path” for the runway; however, it was “somewhat close to tall trees on the left.” During recovery from a second forward slip, the glider had a slight left bank angle, which caused it to track closer to the trees. The wings then leveled, and the glider impacted trees with its left wing, rotated, and pitched steeply nose-down before it impacted terrain. Examination of the accident site revealed that the glider impacted a tree 254 ft left of the runway 25 centerline, and 390 ft short of the runway threshold (the intended landing area was in the grass to the left of runway 25). The tree was about 60-70 ft tall and displayed broken branches about 10 to 15 ft below its top. The tree was about 20 ft taller than those surrounding it in the tree line. A debris path of broken branches extended parallel to the tree line in a grass field. The path was 25 ft to the right of the trees, was about 165 ft long, and was oriented along a true heading of 234°. There were no glider components or ground scars found along the path, and the glider came to rest inverted. (See figure 1.) Figure 1 - Scene Diagram The glider was largely intact, and all major components were present at the accident site. Both wings displayed leading edge impact/crushing damage outboard of the wing struts. Tree bark fragments were present in the damaged area of the left wing. The fuselage was buckled and twisted toward the right about 2 ft aft of the wing’s trailing edge. The upper 10 inches of the vertical stabilizer and rudder were impact damaged. The forward sections of the cockpit and canopy were crushed and fragmented forward of the front seat. The front seat was relatively undamaged, and the4-point harness was intact and remained attached to each of its mounting points. Flight control continuity was established for all primary flight controls from the cockpit to the control surfaces. All cables and push/pull tubes remained connected, and the elevator, aileron, and rudder could all be moved from the cockpit controls, with binding. The speed brake control lever was in the retracted position and the speed brakes were not extended. Toxicology testing of the pilot was performed by the Federal Aviation Administration (FAA) Forensic Sciences Laboratory. Ethanol, drugs of abuse, and carboxyhemoglobin were not detected. No medications were found that would have posed a hazard to flight safety. Remnants of a bird’s foot were found at the base of the struck tree. No bird remains were visible on any of the glider’s components. Canopy fragments were sent to the Smithsonian Institution’s Feather Identification lab for DNA testing, along with photos of the foot. No viable avian DNA was detected on the canopy fragments. The foot was identified as chicken (Gallus gallus domesticus). ## Aircraft - Registration: [N17879](https://openairdocs.org/deregistered/N17879-2022-12-03), registration cancelled 2022-12-03, S/N 249, built 1972 (OpenAirDocs) - Reported make and model: SCHWEIZER SGS 2-33A - Registry model: [Schweizer SGS 2-33A](https://openairdocs.org/model/schweizer-sgs-2-33a) (registry code 8051606) (OpenAirDocs) - Registry engine: [NONE](https://openairdocs.org/engine/none) (registry code 00000, none) (OpenAirDocs) - Category: Glider - Serial number: 249 - Year built: 1972 - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Jersey Ridge Soaring LLC - Registered owner: Jersey Ridge Soaring LLC - Airworthiness certificate: Standard, Normal - Destination: Same as departure - Airport: 1N7, Blairstown Airport, runway 25, 3,112 × 70 ft, asphalt - Equipment: None ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 71; injuries: fatal; student; last flight review May 15, 2022; seat: front; restraint: 4-point; toxicology performed; flight hours: 19.6 total, 14.7 in this make and model, 2.3 in the last 90 days, 2.3 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 210° at 8 knots - Temperature: 79 °F, dew point 63 °F - Altimeter: 29.83 inHg - Observed at: 12N, 12 nm away - METAR: K12N 151854Z AUTO 21008KT 26/17 A2983 RMK AO1 SLP092 T02610167 ## 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 20220515006679A](https://openairdocs.org/incident/20220515006679A), May 15, 2022: Schweizer SGS 2-33A, Blaistown, NJ, Substantial damage, 1 fatal. Student glider pilot [privacy data omitted] was on his second solo flight at the Blairstown Airport (1N7) located in new jersey. The flight was supervised by… ## Docket (9 files) The files NTSB released with the investigation on May 30, 2024, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=105076. 20.2 MB in all. - Witness statements (item 1, PDF, 2 pages, 109 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17093975&FileExtension=pdf&FileName=01-02%20Witness%20statements_ERA22FA227-Rel.pdf - Pilot logbook (item 2, PDF, 17 pages, 8.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17093834&FileExtension=pdf&FileName=02-01%20Pilot_logbook_Redacted-Rel.pdf - Excerpts from maintenance logbook (item 3, PDF, 16 pages, 6.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17096055&FileExtension=pdf&FileName=03-01%20Excerpts%20from%20Maintenance%20Logbook_Redacted_print_Redacted2b-Rel.pdf - Investigative photographs (item 4, PDF, 7 pages, 6 photos, 2.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17093535&FileExtension=pdf&FileName=06-00%20Investigative%20Photographs_ERA22FA227-Rel.pdf - Scene diagram (item 5, PDF, 1 page, 370 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17098806&FileExtension=pdf&FileName=06-01%20Scene%20Diagram-Rel.pdf - Wreckage examination report (item 6, PDF, 2 pages, 69 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17094083&FileExtension=pdf&FileName=06-02%20Airframe%20Examination_ERA22FA227-Rel.pdf - Smithsonian feather identification lab report (item 7, PDF, 2 pages, 1 photo, 474 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17094424&FileExtension=pdf&FileName=06-03%20Smithsonian%20Feather%20Identification%20Lab%20Report%20ERA22FA227_print_Redacted-Rel.pdf - Toxicological report (item 8, PDF, 2 pages, 162 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17094093&FileExtension=pdf&FileName=07-01%20Toxicological_report_ERA22FA227_2022_066_001_print_Redacted-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 9, PDF, 2 pages, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17177038&FileExtension=pdf&FileName=09-02%20NTSB%20Form%206120-15%20Wreckage%20Release%20ERA22FA227_signed_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.