IAD96LA129 · Aerofab Inc. LAKE 250
Aerofab Inc. LAKE 250 · Accident: in flight collision with terrain/water en route
From Patrick Leahy Burlington International Airport (BTV) to Adirondack Regional Airport (SLK)
Event
- NTSB case
- IAD96LA129
- 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
- 0
- 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
Aerofab Inc. LAKE 250
- Aircraft type
- Aerofab LAKE 250
- 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
- N8428F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Patrick Leahy Burlington International Airport (BTV), Burlington, VTTo Adirondack Regional Airport (SLK), Saranac Lake, NY
- 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
- En route · climb to cruise
- 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 terrain/water
- 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
- Pilot in command › Altitude/clearance, not maintained
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was sightseeing, looking for a resort area to land. He stated that his flight was uneventful, until he initiated a climb between two mountain ranges, then he heard the stall warning horn sound. He stated that he was close to the ground, so he did not look inside the cockpit. He stated that when he added full power, the engine sounded normal, but the stall warning horn sounded a second and a third time. Also, he stated that he made a controlled stall-type landing onto the tree tops. According to an FAA safety inspector, the pilot reported that he could not see the ridge clearly due to haze. The accident site was at an approximate elevation of 2900 feet. The height of the mountain was about 3300 feet.
Probable cause
the pilot's improper in-flight planning/decision, which resulted in his failure to ensure that he could maintain sufficient altitude and clearance from mountainous terrain after entering a blind canyon. Haze and the terrain were related factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD96LA129
- Event ID
- 20001208X06529
- Case number
- IAD96LA129
- 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. 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: b3563ba0b5ec0715b22e032f9b8b688c1bc2eabe7c477e9fe666fc0353476045; retrieved 2026-09-21T21:37:34.159Z.