FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA465 · Czech Aircraft Works Spol SRO SPORTCRUISER A

4 Aug 2017 · Salisbury, NC, United States

NMG Aviation Czech Aircraft Works Spol SRO SPORTCRUISER A · Accident: hard landing

From Mid-Carolina Regional Airport (KRUQ) to Mid-Carolina Regional Airport (KRUQ)

Report a problem

Event

NTSB case
GAA17CA465
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Czech Aircraft Works Spol SRO SPORTCRUISER A

Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N777NG
Operator
NMG Aviation
Onboard fatalities
Unknown
Route
From Mid-Carolina Regional Airport (KRUQ), Salisbury, NCTo Mid-Carolina Regional Airport (KRUQ), Salisbury, NC
Aircraft age
About 10 years (built 2007)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Environmental issues › Task environment
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot reported that he had departed with the intent to perform touch-and-go takeoffs and landings. After takeoff, he realized that the canopy was not latched. He struggled to maintain airplane control in the pattern, but he was able to land normally.

The student pilot then checked the latch handle, and he believed that he had secured the canopy correctly. He took off and flew one pattern but just before landing, the canopy opened and obstructed the pilot's view of the runway.

The airplane landed hard and bounced, and the pilot aborted the landing.

The student pilot flew a third pattern and made an approach over the runway centerline, "slightly above stall airspeed." The airplane landed hard on the runway, and the right main landing gear (MLG) and the nose landing gear separated from the airplane. The airplane skidded to a stop on the runway.

The airplane sustained substantial damage to the right MLG attachment points and the right-wing spar.

The student pilot asserted that the canopy latch was down during the takeoffs but was not seated correctly. For the latch to seat correctly, "the canopy itself needed to be pushed up so that gravity seated the canopy."

The airplane was equipped with a full-width clear canopy, hinged in the front and tipped forward for entry to the cockpit.

The manually operated canopy was supposed to be closed by the pilot by reaching above their head and grabbing the handle identified by the manufacturer's illustrated parts catalogue as SF0730N. Per the photographs provided by Federal Aviation Administration (FAA) aviation safety inspectors, the handle was not installed on the canopy.

The canopy security latches consisted of two metal claw-type latches that were mechanically moved forward to secure the canopy to the fuselage. The canopy latches were moved forward to the secure position when the pilot lowered the canopy "T" handle. The "T" handle was affixed to the baggage compartment front wall in the cockpit between the left and right seats just above the arm rest and just below the pilot headset audio input jacks.

The student pilot's head set control unit was about 4 inches long by 1 inch in diameter. Photographs taken shortly after the accident and provided by FAA inspectors revealed that the control unit was lodged underneath the "T" handle.

The student pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The physical interference of the student pilot’s headset control unit with the canopy, which prevented the canopy latches from seating properly and resulted in the canopy opening in flight and the subsequent hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA465
Event ID
20170803X23252
Case number
GAA17CA465
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 006cda1140510555aaf810bca011a7523458b2c397e0b3cbcf9bdb9079fd3c34; retrieved 2026-09-16T05:39:25.669Z.