ATL03LA138 · Great Lakes 2T-1A-2
Great Lakes 2T-1A-2 · Accident: in flight collision with object on approach
From Morristown Regional Airport (MOR) to Gwinnett County Briscoe Field (LZU)
Event
- NTSB case
- ATL03LA138
- 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
Great Lakes 2T-1A-2
- Aircraft type
- Great Lakes 2
- 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
- N22TE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Morristown Regional Airport (MOR), Morristown, TNTo Gwinnett County Briscoe Field (LZU), Lawrenceville, GA
- 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
- In flight collision with object
- 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
- 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 › Clearance, 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
According to the pilot, she was attempting to land on the right side of a private airstrip. The pilot stated that during the final approach to land, the airplane drifted to the right of the runway and hit a tree. The airplane fell to the ground and the wheel of the airplane lodged into a dirt berm and nosed over. Examination of the airplane revealed the vertical stabilizer and the upper wings were damaged. The right landing gear collapsed. The pilot stated there were no mechanical problems with the airplane prior to the accident.
Probable cause
The pilot's failure to maintain clearance during the final approach to land which resulted in an inflight collision with a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL03LA138
- Event ID
- 20030923X01575
- Case number
- ATL03LA138
- 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: 9d82d9a0f332750e29ac36e3a8dbeeaca631d16888878376b52e230e0db67593; retrieved 2026-09-22T08:32:25.436Z.