NYC01LA183 · Beech BE-36
Charlotte Flying Club Beech BE-36 · Accident: on ground/water collision with object during takeoff
From Biddeford Municipal Airport (B19) to Westchester County Airport (HPN)
Event
- NTSB case
- NYC01LA183
- 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
Beech BE-36
- Aircraft type
- Beechcraft BE-36
- 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
- N3680U
- Operator
- Charlotte Flying Club
- Onboard fatalities
- Unknown
- Route
- From Biddeford Municipal Airport (B19), Biddeford, METo Westchester County Airport (HPN), White Plains, NY
- 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
- On ground/water collision with object
- 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 › Preflight planning/preparation, inadequate
- Pilot in command › Removal of control/gust lock(s), not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said he performed an engine run-up prior to takeoff without utilizing the airplane's checklist as he normally would. During the takeoff roll, the pilot was not able to pull-back on the control column. The airplane continued down the runway, until it departed the end of the runway and impacted several small trees. Post accident examination of the airplane revealed that the control column lock was installed in the control column. The pilot reported 1,300 hours of total flight experience, which included 200 hours in make and model. He was also a certified flight instructor.
Probable cause
The pilot's inadequate preflight inspection, which resulted in an attempted takeoff with a control column lock installed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA183
- Event ID
- 20010723X01475
- Case number
- NYC01LA183
- 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: b874a1b3e4fae682a9f1d2270f8a36ab01406cfdabd71e099a26e9d9b0c25454; retrieved 2026-09-22T11:44:32.336Z.