- Date
- December 20, 1967
- Place
- Ames, KS · AMES, KS
- Injuries
- 3 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N7048TCessna 172
- Status
- Completed · report February 6, 1968
- Report
- Brief approved by the director
- Case key
- 112640
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-4468 67/12/20 AMES,KANS CESSNA 172 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 44, 345 TIME - 1130 N7048T PX- 0 0 2 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 262 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - BRICHAT STRIP TYPE OF ACCIDENT PHASE OF OPERATION HARD LANDING LANDING: LEVEL OFF/TOUCHDOWN GEAR COLLAPSED LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER LEVEL OFF FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - UNKNOWN/NOT REPORTED SKY CONDITION CEILING AT ACCIDENT SITE SCATTERED 5000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE RELATIVE BEARING OF WIND NONE HEAD WIND 338-022 DEGREES TEMPERATURE-F WIND DIRECTION-DEGREES 40 180 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 35 VFR TYPE OF FLIGHT PLAN NONE REMARKS- HEADWIND 25K GUSTING TO 35K.
Aircraft
- Registration
- N7048T
- Reported as
- Cessna 172
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Brichat Strip
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.