NYC08LA024 · Blondin 601HDS
Blondin 601HDS · Accident: loss of control in flight while maneuvering
From Chorman Airport (D74) to Crisfield-Somerset County Airport (W41)
Event
- NTSB case
- NYC08LA024
- 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
- 2 · 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
Blondin 601HDS
- Aircraft type
- Blondin 601
- 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
- N27S
- Operator
- Raymond Blondin
- Onboard fatalities
- Unknown
- Route
- From Chorman Airport (D74), Farmington, DETo Crisfield-Somerset County Airport (W41), Crisfield, MD
- 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
- Maneuvering
- 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 in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Witnesses described the engine sound during the takeoff roll and initial climb as "normal," "strong," and continuous with no interruption. The takeoff roll was "much longer than usual" and the airplane used about two thirds of the 3,588 feet of paved runway before it began a very shallow climb. The airplane drifted right of the runway centerline and flew around the east side of a grove of trees off the departure end. The airplane then banked to its left "in an apparent attempt to return to the airport," turned to the west, disappeared from view behind the trees, and then reappeared above the trees in a steep left bank. According to one witness, "[The airplane] popped up in a very steep left bank (both wings were vertical like a knife edge)." The airplane then disappeared from view, the sounds of impact were heard, and a large smoke plume appeared. No usable information could be gathered from the cockpit, nor could control continuity be established due to extensive fire damage. Examination of aerial photographs revealed that the airport and the grove of trees were surrounded by flat, open, cultivated fields suitable for forced landing.
Probable cause
The reason for this occurrence could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08LA024
- Event ID
- 20071121X01825
- Case number
- NYC08LA024
- 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: f98df901cce1d8b67432818497d542c47c9a1b0df8ab053fbdc462cc5b26d99f; retrieved 2026-09-20T16:08:08.468Z.