ERA21LA035 · Grumman GA7
Majestic Aviation Grumman GA7 · Accident: controlled flight into terrain/object (CFIT) on approach
From Burlington Alamance Regional Airport (BUY) to Chautauqua County-Jamestown Airport (JHW)
Event
- NTSB case
- ERA21LA035
- 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
- 3 · 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
- Instrument Meteorological Cond
Grumman GA7
- Aircraft type
- Grumman GA7
- 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
- N791GA
- Operator
- Majestic Aviation
- Onboard fatalities
- Unknown
- Route
- From Burlington Alamance Regional Airport (BUY), Burlington, NCTo Chautauqua County-Jamestown Airport (JHW), Jamestown, NY
- Aircraft age
- About 41 years (built 1979)
- 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
- Approach · IFR final approach
- 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
- Controlled flight into terrain/object (CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot rented the airplane and completed a long cross-country flight 4 days before the accident. Before the return (accident) flight, the pilot discussed weather decisions and avoiding icing conditions with his flight instructor via telephone. The instructor subsequently checked a commercial website and realized that the pilot had departed on the return flight. He hoped that the pilot would divert due to the poor weather conditions and sent him a text message to that effect.
Review of air traffic control data revealed that, while approaching the destination airport, the pilot provided a pilot report indicating that the airplane was in and out of clouds, updrafts, downdrafts, snow, and light-to-moderate turbulence. The pilot then flew an instrument approach to the destination airport, but radar contact was lost while the airplane was on a 1-mile final approach to the runway.
Review of the last 1 minute of data revealed an approximate 500 ft-per-minute descent, consistent with the pilot’s descent on the instrument approach. A witness who lived near the airport reported that he could not see well due to wind and snow and did not initially hear the airplane. He then heard loud engine noise for 10 to 15 seconds followed by silence. The wreckage was located the following day about 1/2 mile from the runway threshold. The wreckage path was consistent with a gradual descent into trees.
Examination of the airframe, engines, and recorded data did not reveal any preimpact mechanical malfunctions. The last automatic dependent surveillance-broadcast target indicated an altitude of 2,250 ft mean sea level (msl), which was 527 ft above airport elevation. The recorded weather at the airport 2 minutes after the accident included scattered clouds at 500 ft above ground level and 3/4-mile visibility in light snow and mist. Review of the instrument approach chart revealed a minimum descent altitude of 2,100 ft msl at a distance of 1.1 miles (with minimum visibility 1/2 mile) from the airport with a local altimeter setting and no vertical guidance. If vertical guidance was used on the GPS, the minimum descent altitude was 1,921 ft msl (with minimum visibility 1/2 mile) with local altimeter setting. Although the last target was recorded about 1 mile from the runway threshold and the wreckage was located about 1/2 mile from the runway threshold, there were no data available from the last target to the wreckage. The pilot’s logbook was not recovered, and neither his total time nor his recent instrument flight rules experience could be determined. The circumstances of the accident are consistent with the pilot’s continued descent below the minimum descent altitude while conducting an instrument approach in instrument meteorological conditions, which resulted in controlled flight into terrain.
Probable cause
The pilot’s continued descent below the minimum descent altitude while conducting an instrument approach in instrument meteorological conditions, which resulted in controlled flight into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA035
- Event ID
- 20201102102223
- Case number
- ERA21LA035
- 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, coordinates, cause areas. 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: f3b9178de00b3260cce6fb663225e8bbda1f6ba74df77753eec2293ec63886ac; retrieved 2026-09-15T07:21:56.241Z.