GAA18CA375 · Taylorcraft F19
Taylorcraft F19 · Accident: landing area undershoot
From Lake Hood Seaplane Base (LHD) to Anchorage, AK
Event
- NTSB case
- GAA18CA375
- 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
Taylorcraft F19
- Aircraft type
- Taylorcraft F19
- 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
- N3570T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lake Hood Seaplane Base (LHD), Anchorage, AKTo Anchorage, AK
- Aircraft age
- About 43 years (built 1975)
- 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
- Landing
- 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
- Landing area undershoot
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the float-equipped airplane reported that, during a flight at dusk with high, gray overcast clouds, he circled over a lake and began the approach to land. He added that his depth perception was off, he misjudged the approach, and the airplane struck a tree.
The airplane sustained substantial damage to both wings.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The automated weather observation station located about 6 miles northwest of the accident site reported that, about 23 minutes after the accident, the wind was calm, scattered clouds at 4,100 ft, and overcast clouds at 6,000 ft.
Probable cause
The pilot’s failure to maintain a proper approach path during landing in dusky, flat light conditions, which resulted in a tree strike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA375
- Event ID
- 20180625X24533
- Case number
- GAA18CA375
- 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. 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: a83ec1f9a791c0193f04e4c3dc6bd8dcbfc8ee0f4bfa0ab1fe58357fb449a782; retrieved 2026-09-16T07:39:53.415Z.