SEA06MA047 · Cessna 560
Goship Air Cessna 560 · Accident: in flight collision with object during landing
From Friedman Memorial Airport (KSUN) to McClellan-Palomar Airport (KCRQ)
Event
- NTSB case
- SEA06MA047
- 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
- 4 · 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 560
- Aircraft type
- Cessna 560
- 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
- N86CE
- Operator
- Goship Air
- Onboard fatalities
- Unknown
- Route
- From Friedman Memorial Airport (KSUN), Hailey, IDTo McClellan-Palomar Airport (KCRQ), Carlsbad, 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
- Landing · aborted
- 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
- In flight 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
- Destroyed
Cause areas
- Pilot in command › 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
Air traffic control cleared the flightcrew for the instrument landing system (ILS) approach to runway 24, which was 4,897 feet long. The flightcrew then reported that they had the runway in sight, cancelled their instrument flight rules (IFR) clearance, and executed a visual flight rules (VFR) approach in VFR conditions to the airport. The reported winds favored a landing toward the east, onto the opposite runway (runway 6). During the approach, after a query from the first officer, the captain indicated to the first officer that he was going to "...land to the east," consistent with the reported winds. However, the final approach and subsequent landing were made to runway 24, which produced a six-knot tailwind. During the approach sequence the captain maintained an airspeed that was approximately 30 knots higher than the correct airspeed for the aircraft's weight, resulting in the aircraft touching down about 1,500 feet further down the runway than normal, and much faster than normal. The captain then delayed the initiation of a go-around until the first officer asked if they were going around. Although the aircraft lifted off the runway surface prior to departing the paved overrun during the delayed go-around it impacted a localizer antenna platform, whose highest non-frangible structure was located approximately 304 feet past the end of the runway, and approximately two feet lower than the terrain at the departure end of the runway. The aircraft continued airborne as it flew over downsloping terrain for about 400 more feet before colliding with the terrain and a commercial storage building that was located at an elevation approximately 80 feet lower than the terrain at the end of the runway. The localizer antenna platform was located outside of the designated runway safety area, and met all applicable FAA siting requirements. The captain had type 2 diabetes, for which he took oral medication and monitored blood sugar levels. He did not reveal his history of diabetes to the FAA. The captain's post-accident toxicology testing was consistent with an elevated average blood sugar level over the previous several months; however, no medical records of the captain's treatment were available, and the investigation could not determine if the captain's diabetes or treatment were potentially factors in the accident. The captain of the accident flight was the sole owner of a corporation that was asked by the two owners of the accident airplane to manage the airplane for them under a Part 91 business flight operation. The two owners were not pilots and had no professional aviation experience, but they desired to be flown to major domestic airports so that they could transfer and travel internationally via commercial airlines. One of the two owners stated that the purpose of the accident flight was to fly a businessman to a meeting, and to also transport one of the owner's wives to visit family at the same destination. According to one of the owners, the businessman was interested in being a third owner in the accident airplane, so the owner permitted the businessman to fly. The owner also stated that the accident pilot told him that the passenger would pay for expenses directly related to the operation of the airplane for the flight (permitted under FAA Part 91 rules), and an "hourly fee" (prohibited under FAA Part 91 rules); however, no documentation was found to corroborate this statement for the accident flight or previous flights.
Probable cause
The captain's delayed decision to execute a balked landing (go-around) during the landing roll. Factors contributing to the accident include the captain's improper decision to land with a tailwind, his excessive airspeed on final approach, and his failure to attain a proper touchdown point during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06MA047
- Event ID
- 20060202X00149
- Case number
- SEA06MA047
- 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: ea6c8b121941b20680da496b06c74ee70bb605b4899df5e3ce38ef4b5f718487; retrieved 2026-09-20T17:35:07.436Z.