FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX08CA163 · Cessna 172P

4 Jun 2008 · Bremerton, WA, United States

Wings Aloft Cessna 172P · Accident: hard landing

From Bremerton National Airport (KPWT) to an unrecorded destination

Report a problem

Event

NTSB case
LAX08CA163
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

Cessna 172P

Aircraft type
Cessna 172
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
N52807
Operator
Wings Aloft
Onboard fatalities
Unknown
Route
From Bremerton National Airport (KPWT), Bremerton, WATo 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
Defining eventThe 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

  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The student pilot was practicing touch-and-go landings on his first solo flight. After one successful touch-and-go landing, he made a second approach. He maintained 65 knots, lowered 30 degrees of flaps, and followed the glide path. After the airplane touched down on the main gear, it ballooned and the student pilot applied slight forward pressure on the yoke. The nose gear and propeller struck the ground, and the airplane bounced back into the air. He lost control of the airplane as the nose gear and propeller struck the runway several more times. He braked heavily, and the airplane skidded to the side of the runway before stopping.

Probable cause

The student pilot's inadequate recovery from a bounced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX08CA163
Event ID
20080701X00959
Case number
LAX08CA163
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 52e0433af1468bcc8794d3ea861a99ca139c5257c2c565c5bc6539c7712e66b3; retrieved 2026-09-15T09:50:42.104Z.