FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL01LA024 · Cessna 152

18 Jan 2001 · ST. AUGUSTINE, FL, United States

Cessna 152 · Accident: loss of control on ground/water during landing

From Keystone Heights Airport (42J) to Northeast Florida Regional Airport (SGJ)

Report a problem

Event

NTSB case
ATL01LA024
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
Instrument Meteorological Cond

Cessna 152

Aircraft type
Cessna 152
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
N704ZF
Operator
Bolker Fritz
Onboard fatalities
Unknown
Route
From Keystone Heights Airport (42J), Keystone, FLTo Northeast Florida Regional Airport (SGJ), ST. AUGUSTINE, FL
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 · landing roll
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
Loss of control on ground/water
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 › Aircraft control, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the student pilot, he was conducting a supervised solo cross-country flight. Upon arriving at St. John County Airport, he established a visual approach to runway 13 for a full-stop landing. During the landing roll-out, the student pilot stated that the airplane entered a fog bank, veered off the left side of the runway, and collided with an airport sign. Witnesses stated that, at the time of the accident there was no fog in the area, or surrounding the airport. Weather conditions were clear with 10 miles visibility. Witnesses stated that, the pilot locked up the brakes and tried to exit the runway at the first taxiway. Inspection of the airplane did not reveal any preexisting discrepancies.

Probable cause

The pilots failure to maintain directional control during the landing roll, which resulted in the collision with the airport sign.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL01LA024
Event ID
20010124X00353
Case number
ATL01LA024
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. 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: ca518a6d489f5b91930c46b96dc53696e9cc61637b6d6f3faa66fd1669c2ae57; retrieved 2026-09-22T12:13:33.374Z.