ANC97LA101 · Boeing D75N1
Boeing D75N1 · Accident: in flight collision with object during landing
Event
- NTSB case
- ANC97LA101
- 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
Boeing D75N1
- Aircraft type
- Boeing D75
- 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
- N60821
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- Landing · aborted
- 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); Wire, transmission
- 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 › In-flight planning/decision, inadequate
- Pilot in command › Recovery from bounced landing, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was landing in an uphill direction on a small grass airstrip. The airstrip, located about 880 feet mean sea level, was 1,200 feet long, and about 80 feet wide. The pilot reported he bounced the airplane during the initial touchdown. He applied full power to abort the landing. The pilot began a left turn but the airplane did not climb above tall trees surrounding the airport. The airplane began colliding with several trees about 50 feet above the ground, about 1/8 mile from the runway. The airplane then collided with power lines adjacent to a road, and then continued into numerous trees. The airplane's wings were torn off the fuselage. The airplane received additional damage to the fuselage and tail assembly. The pilot reported the weather conditions at the time of the accident included calm winds, with a temperature of about 80 degrees F.
Probable cause
The pilot's inadequate recovery from a bounced landing and his inadequate in-flight planning/decision making during an aborted landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC97LA101
- Event ID
- 20001208X08275
- Case number
- ANC97LA101
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1997-07-11.
- API snapshot SHA-256: bf0d2adc3adbe090ef74a36fffbe17634c8b9c144619a98abc929263cb775dc5; retrieved 2026-09-22T19:11:26.131Z.