ATL07CA061 · Harrison Robert J. Longez
Harrison Robert J. Longez · Accident: loss of control in flight on approach
From Foothills Regional Airport (MRN) to Foothills Regional Airport (MRN)
Event
- NTSB case
- ATL07CA061
- 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
Harrison Robert J. Longez
- Aircraft type
- Harrison Robert LONGEZ
- 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
- N17XZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Foothills Regional Airport (MRN), Morganton, NCTo Foothills Regional Airport (MRN), Morganton, NC
- Aircraft age
- Not recorded
- 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 · VFR pattern final
- First occurrenceThe 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall; Tree(s)
- 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
- Pilot in command › Airspeed, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane collided with trees short of the runway. According to the pilot, following a few touch and gos, he left the pattern for about 40 minutes and returned to the airport. Upon arrival at the airport he entered a right downwind pattern about 2000 feet msl for runway 21. He stated that the downwind was normal and once he was abeam the numbers he turned base and "believed the final leg was a bit longer then usual". He stated that as he got close to the runway he was low and increased the throttle to full power, "I seemed to drop precipitously and the tips of the trees seemed level with my wheels. At that time the right wing seemed to hit something and somehow I was on the ground". He stated that the last airspeed he was aware of was 85-90 miles per hour. He said that he shut the engine off, and got out of the airplane, walked about 20 feet and sat down. According to a witness, he observed the airplane in what appeared to be a normal approach to landing on runway 21, at an altitude of 200 feet. The witness stated that he was located in front of a large corporate hangar and the airplane was approximately 1/2 mile away. He said he observed the right wing drop sharply with a noticeable decrease in altitude followed by recovery, then a second drop of the right wing more severe this time and the airplane dropped completely below the tree line. The witness stated that he heard the application of full engine power followed by a single loud impact then almost immediately the sound of several impacts mixed with the "unmistakable sound of multiple propeller strikes" then silence. The witness stated that he located the wreckage at a distance of approximately 200 yards off the approach end of the runway. The witness stated that it took several minutes to reach the airplane and at that point he found the pilot outside the airplane, standing by the left wing, appearing confused. The witness stated that the pilot told him that "I'm okay, I just got too slow and stalled it." There were no mechanical problems reported by the pilot or discovered during the post-accident examination of the airplane.
Probable cause
The pilot's failure to maintain an adequate airspeed that resulted in an inadvertent stall, and subsequent inflight collision with trees and the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL07CA061
- Event ID
- 20070523X00621
- Case number
- ATL07CA061
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 4f1aafe2734b94a8b55400bedda34e0a4718efa31509a5c67aed710bb655a551; retrieved 2026-09-21T08:50:12.961Z.