DEN04LA148 · Smith, Ted Aerostar 601P
Smith, Ted Aerostar 601P · Accident: hard landing
From Rocky Mountain Metropolitan Airport (BJC) to an unrecorded destination
Event
- NTSB case
- DEN04LA148
- 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
Smith, Ted Aerostar 601P
- Aircraft type
- Smith Ted Aerostar 601
- 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
- N200FF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (BJC), Broomfield, COTo 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 · flare/touchdown
- 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
- Hard landing
- 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 › Flare, improper
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said he was asked by the tower to make a short approach. He was then asked to make his right base turn, such that he had to continue his turn to roll out on final over the runway. The pilot said he leveled the wings and had a hard landing. The pilot said that the right main landing gear collapsed and the airplane slid off the left side of the runway. An examination of the airplane showed the left main landing gear strut was broken and pushed upward through the top of the left wing engine nacelle. The right wing was broken upward at the wing root. Both propellers' blades showed torsional bending and chordwise scratches. Flight control continuity was confirmed. No other anomalies were found.
Probable cause
the pilot's improper in-flight planning/decision to accept a short traffic pattern and the improper flare resulting in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN04LA148
- Event ID
- 20040928X01510
- Case number
- DEN04LA148
- 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: bb7ff68a95a8341dcf2eb68dd6acbfaa0a993f77c5493787311c666ded21fc7d; retrieved 2026-09-22T06:41:05.490Z.