ATL07FA030 · Cessna 414A
Cessna 414A · Accident: in flight collision with object on approach
From Palm Beach County Glades Airport (KPHK) to Gwinnett County Briscoe Field (KLZU)
Event
- NTSB case
- ATL07FA030
- 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
Cessna 414A
- Aircraft type
- Cessna 414
- 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
- N62950
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Palm Beach County Glades Airport (KPHK), Pahokee, FLTo Gwinnett County Briscoe Field (KLZU), 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
- 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 › IFR procedure, not followed
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 Atlanta Air Route Traffic Control Center (ARTCC) personnel, the pilot was given the current weather information before attempting his first instrument approach into Gwinnett County Airport-Briscoe Field (LZU), Lawrenceville, Georgia, which included: winds calm, visibility 1/2-mile in fog, and ceiling 100 feet. The pilot acknowledged the current weather information and elected to continue for the instrument landing system (ILS) runway-25 approach. During the first landing attempt, the pilot reported that he was going to execute a missed approach, but that he saw the airport below and wanted to attempt another approach. The ARTCC controller provided the pilot with radar vectors back to the ILS runway-25 approach and again updated the pilot with current weather conditions. During the second approach the tower controller advised the pilot that he was left of the runway-25 centerline. Shortly after the pilot acknowledged that he was left of the centerline, the tower controller saw a bright "orange glow" off of the left side of the approach end of runway 25. Although the weather conditions were below approach minimums for the runway 25-approach, the pilot elected to attempt the landing. A flight inspection of the ILS was completed on December 26, 2006, and the results of the inspection revealed that the ILS runway-25 approach system was satisfactory. Examination of the airframe, flight control system components, engines and system components revealed no evidence of preimpact mechanical malfunction.
Probable cause
The pilot's failure to follow the instrument approach procedure. Contributing to the accident was the pilot's descent below the prescribed decision height altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL07FA030
- Event ID
- 20070111X00043
- Case number
- ATL07FA030
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-12-26.
- API snapshot SHA-256: fee2111ee32fd408f58485b49779a56c3ab97d9e8730eb9a2bd254f1b383237b; retrieved 2026-09-20T16:56:18.971Z.