# Accident 20000915010059A: Cessna 170B, Alturas, CA, September 15, 2000 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: September 15, 2000, 17:50 local time - Place: Alturas, CA - Airport: Alturas Municipal - Damage: Substantial damage - Phase of flight: Level Off Touchdown - Operating rules: General operating rules (Part 91) - Location: 41.4309° N, 120.5291° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=41.4309&lon=-120.5291&mi=10 - Aircraft: N4590C, a cancelled registration (https://openairdocs.org/deregistered/N4590C-2019-01-31) (OpenAirDocs) - Registry model: Cessna 170B (registry code 2072306, https://openairdocs.org/model/cessna-170b) (OpenAirDocs) - Reported make and model: CESSNA 170B - Reported engine: CONT C1452 - People aboard: 4 - Fatal injuries: 0 - Pilot flight hours: 628 total, 38 in this make and model, 8 in the last 90 days - NTSB investigation: [NTSB LAX00LA340](https://openairdocs.org/ntsb/LAX00LA340) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20000915010059A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) THE PILOT LANDED ON RUNWAY 31 AND ENCOUNTERED A GUSTY CROSSWIND, CAUSING HIM TO LOOSE CONTROL. DAMAGE TO THE LEFT LANDING GEAR, LEFT WING, FUSELAGE AND PROPELLER RESULTED. ASOS WEATHER 50 MINUTES PRIOR TO THE ACCIDENT WAS 260 DEGREES @ 8 KTS. RUNWAY OPTIONS WERE 31 AND 21, EACH CAUSING A 50 DEGREE CROSSWIND COMPONENT. (.4) ON SEPTEMBER 15, 2000, ABOUT 1750 HOURS PACIFIC DAYLIGHT TIME, A CESSNA 170B, N4590C, WAS SUBSTANTIALLY DAMAGED DURING LANDING AT ALTURAS, CALIFORNIA. NEITHER THE COMMERCIAL RATED PILOT NOR THE THREE PASSENGERS WERE INJURED. THE REGISTERED OWNER OPERATED THE AIRPLANE UNDER 14 CFR PART 91. VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND A VISUAL FLIGHT PLAN WAS FILED FOR THE PERSONAL FLIGHT. THE FLIGHT ORIGINATED AT CONCORD, CALIFORNIA, AT 1530. THE PILOT STATED THAT HE WAS UNABLE TO LOCATE A WINDSOCK WHILE CIRCLING THE UNCONTROLLED AIRPORT. HE HAD OBTAINED A PREFLIGHT WEATHER BRIEFING FROM THE FEDERAL AVIATION ADMINISTRATION RED BLUFF FLIGHT SERVICE STATION, WITH NO ADVERSE WEATHER CONDITIONS NOTED. NO LOCAL AREA WIND INFORMATION WAS OBTAINED. HE ESTABLISHED A LEFT PATTERN FOR RUNWAY 31; ON FINAL APPROACH HE DETERMINED THERE WAS A LEFT CROSSWIND FOR WHICH HE ESTABLISHED A CRAB ANGLE. ON TOUCHDOWN, THE LEFT WING CAME UP, RESULTING IN THE RIGHT WING SCRAPING THE RUNWAY AND A LOSS OF DIRECTIONAL CONTROL. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB LAX00LA340](https://openairdocs.org/ntsb/LAX00LA340), Sep 16, 2000: Cessna 170B (N4590C), Alturus, CA, substantial damage. Probable cause: The pilot's inadequate compensation for the wind, and his failure to maintain directional control of the airplane during landing. A factor was the faded improperly maintained windsock. ## Other reports on N4590C (3) Matched to the same aircraft by N-number and date. - [Accident 20100722041159A](https://openairdocs.org/incident/20100722041159A), Jul 22, 2010: Cessna 170B (N4590C), Palmer, AK, Substantial damage. The pilot stated that he spotted a back country airstrip and wanted to make some approaches without landing. On initiating a go around as he had planed, the… - [Accident 19970126001049A](https://openairdocs.org/incident/19970126001049A), Jan 26, 1997: Cessna 170B (N4590C), Toledo, WA, Substantial damage. Left wing raised landing in crosswind. Used brakes. Nosed over. Wind light. Low time pilot lacked skill in type. - [Accident 19730526016839A](https://openairdocs.org/incident/19730526016839A), May 26, 1973: Cessna 170B (N4590C), Auburn, WA, Substantial damage From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.