FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC03LA059 · Cessna 152

28 Feb 2003 · Columbus, OH, United States

Cessna 152 · Accident: undershoot on approach

From The Ohio State University Airport - Don Scott Field (OSU) to The Ohio State University Airport - Don Scott Field (OSU)

Report a problem

Event

NTSB case
NYC03LA059
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 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
N170SU
Operator
Unknown
Onboard fatalities
Unknown
Route
From The Ohio State University Airport - Don Scott Field (OSU), Columbus, OHTo The Ohio State University Airport - Don Scott Field (OSU)
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
Approach · VFR pattern final
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
Undershoot
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

  • Dual student › Distance/altitude, misjudged
  • Pilot in command(cfi) › Remedial action, delayed

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

NTSB narrative

A flight instructor and student pilot had been performing touch and go landings on runway 27R, which was 2,994 feet long and 100 feet wide. During the accident approach, the student had set 20 degrees of flaps and established 62 knots of indicated airspeed. The CFI observed the airplane descend below the "glidepath," and instructed the student pilot to add power. After a few seconds, the student added about 50 rpms of power, and the CFI told the student to add more power. When the student didn't respond, the CFI attempted to add power himself; however, the student's hand remained over the throttle, and he was unable to add power. The CFI then started to flare the airplane for landing. The airplane touched down about 20 feet prior to the runway in snow, where it pitched forward on its nose, and the nose gear collapsed. The winds at the airport were reported to be calm.

Probable cause

The student pilot's misjudgment of distance/altitude and the instructor's delayed remedial action,

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC03LA059
Event ID
20030304X00280
Case number
NYC03LA059
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, 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: 7733831b081794ace8ba3a5471c6b57b391109a2b84aa4eb0a796c3d86efc21e; retrieved 2026-09-22T09:33:59.784Z.