The U.S. aircraft register, updated daily
Accidents · NTSB LAX08LA121 · Final report

Cessna 172R accident near S. Lake Tahoe, California, April 19, 2008

On April 19, 2008 at about 11:25 pm local time, a Cessna 172R, registered N2384L, was substantially damaged in an accident during landing (flare/touchdown) near S. Lake Tahoe, California (Lake Tahoe airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's improper flare and subsequent hard landing. Contributing to the accident were the gusty winds and the high density altitude.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 19, 2008 · about 11:25 pm local time
Place
S. Lake Tahoe, California · Lake Tahoe · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172R · all 172Rs on the register
Registration
N2384L · registry record · serial 17280706
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot rented the airplane from the operator for a cross-country flight. The flight experienced gusty winds during the pilot's first attempted landing on runway 18 at the destination airport, which was located in confined valley in mountainous terrain at an elevation of 6,294 feet. Steeply sloped mountains ring the airport except for the approach path for runway 18. He executed a 360-degree turn to attempt a second approach. During the second approach, he noticed "severely decreasing engine performance and gusty winds." The pilot said he executed another 360-degree turn in order to abort the landing and divert away from the airport; however, the airplane was unable to climb, and he landed on runway 18. The pilot stated that upon landing, "the nose of the aircraft pulled erratically but the landing terminated normally and unassisted taxi was performed." The pilot told an employee of the airport's fixed base operator that the airplane had a flat nose wheel tire and he needed someone to repair it. The employee told the pilot that she had seen him circle and then leave the area, and the pilot said that "he was going to leave and continued to circle but could not gain any altitude to get out so had no choice but to come in." The pilot also told her that "he bounced once before he was able to land" the airplane. The mechanic who was tasked with repairing the flat nose wheel tire found extensive damage to the airplane's firewall and nose gear structure. The mechanic stated that after he found and reported the damage, both the pilot and fixed base operator staff told him that the airplane "had made a hard landing upon arrival" the previous day. Reported winds at the airport near the time of the accident were from 210 degrees at 19 knots gusting to 33 knots. The calculated density altitude was 6,955 feet. The operator stated that this accident could have been prevented by "revised dispatch procedures for aircraft traveling to mountainous areas in adverse wind" and "restrictions on what type of aircraft can fly to high density altitude airports."

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Hard landing during landing (flare/touchdown) defining event

The NTSB's findings

  • factor Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › High density altitude › Not specified
  • factor Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Not specified
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land
  • Flight time: 185 hours in all; 150 in this make and model; 40 in the last 90 days; 17 in the last 30 days; 68 as pilot in command
  • Last flight review: July 1, 2007
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 6,422 hours
  • Last inspection: 100-hour inspection, February 1, 2008
  • Maximum gross weight: 2,450 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360 (piston); 0 hours total

The flight

  • Departed from: CCR Concord CA at 9:45 pm
  • Destination: TVL S. Lake Tahoe CA
  • Flight plan: none
  • Runway 18, 8,544 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 210° at 19 knots, gusting 33
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 45°F (7°C), dew point 9°F (-13°C)
  • Altimeter: 29.73 inHg
  • Observation at 11:53 pm from TVL

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Other NTSB records under N2384L the same tail number, which may have belonged to a different aircraft at the time

2005-06-12LAX05CA207 · accident near Santa Maria, CA · substantial damage · no injuries

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.