SEA93FA040 · Dassault-Breguet FALCON 10
Manchester Group Dassault-Breguet FALCON 10 · Accident: overrun during takeoff
From an unrecorded airport to San Diego International Airport (SAN)
Event
- NTSB case
- SEA93FA040
- 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
- 0
- 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
Dassault-Breguet FALCON 10
- Aircraft type
- Dassault Breguet FALCON 10
- 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
- N50TE
- Operator
- Manchester Group
- Onboard fatalities
- Unknown
- Route
- From not recordedTo San Diego International Airport (SAN), San Diego, CA
- 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
- Overrun
- 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
- Copilot/second pilot › Checklist, not followed
- Landing gear, parking brake › Engaged
- Pilot in command › Checklist, not followed
Approximate · Estimated position: the centre of McCall, ID, the place the record names. Not the accident site.
NTSB narrative
DURING THE TAKEOFF ROLL ON A CONTAMINATED RUNWAY, THE COPILOT NOTED A LACK OF ACCELERATION. JUST BEYOND MIDFIELD, THE COPILOT CALLED FOR AN ABORT, HOWEVER, THE PILOT ELECTED TO CONTINUE. THE AIRPLANE DID NOT REACH VR AND THE PILOT ATTEMPTED TO ROTATE THE AIRPLANE AT THE END OF THE RUNWAY. THE AIRPLANE COLLIDED WITH AND TRAVELLED THROUGH A FIVE FOOT HIGH SNOWBANK AND CAME TO REST IN A FIELD APPROXIMATELY 500 FEET FROM THE END OF THE RUNWAY. DURING THE POSTCRASH INVESTIGATION, EVIDENCE INDICATED THAT THE PARKING BRAKE HAD BEEN IN THE INTERMEDIATE POSITION OR 23 PERCENT OF MAXIMUM BRAKING. THE PARKING BRAKE WARNING LIGHT WAS FOUND TO OPERATE CORRECTLY IF THE PANEL LIGHTS WERE SET IN THE BRIGHT LIGHT POSITION. IN THE DIM POSITION, THE WARNING LIGHT WAS INOPERATIVE. DURING THE ON SITE INVESTIGATION, THE PANEL LIGHTS WERE FOUND IN THE DIM POSITION.
Probable cause
THE FAILURE OF THE FLIGHT CREW TO FOLLOW THE CHECKLIST AND RELEASE THE PARKING BRAKE BEFORE TAKEOFF. THE INOPERATIVE PARKING BRAKE WARNING LIGHT AND THE FAILURE OF THE PILOT TO ABORT THE TAKEOFF WERE FACTORS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA93FA040
- Event ID
- 20001211X16240
- Case number
- SEA93FA040
- 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: 06421040f55c94bc3bdeb6ef5389b9544d4db92ff54ebd38950a8918b90dd9cc; retrieved 2026-09-21T14:37:26.329Z.