NYC01LA063 · Cessna 172M
Blue Ridge Flight Center Cessna 172M · Accident: loss of control on ground/water during takeoff
From Farmville Regional Airport (FVX) to Charlottesville Albemarle Airport (CHO)
Event
- NTSB case
- NYC01LA063
- 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 172M
- 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
- N73404
- Operator
- Blue Ridge Flight Center
- Onboard fatalities
- Unknown
- Route
- From Farmville Regional Airport (FVX), Farmville, VATo Charlottesville Albemarle Airport (CHO), Charlottesville, VA
- 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
- Takeoff · roll/run
- 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 › Directional control, not maintained
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 reported that he was on a solo cross-country flight, returning home. He also reported that he used the full length of the runway for takeoff, and the airplane departed the left side of the runway, and struck a cement block. The FAA reported the tracks departed the runway on the opposite side of an intersecting taxiway, about 1600 feet from the beginning of the runway. The tire tracks initially angled off about 20 to 30 degrees to the runway, and then shallowed to become parallel to the runway when the airplane struck a cement block. The tire tracks in the grass were estimated to be about 65 feet long and the cement block was located about 25 feet to the side of the runway. According to the owner's manual the airplane would have required about 630 feet to become airborne.
Probable cause
the failure of the pilot to maintain directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA063
- Event ID
- 20010111X00289
- Case number
- NYC01LA063
- 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: 5b0dbeea0c8cc3152ce48b2a58a3c33e6a51a96c273b1569a3b00e2f6fd49731; retrieved 2026-09-22T12:15:33.384Z.