Southern Nevada Jet Charter Beech 200 accident
Beech 200 · Accident: ground collision while taxiing
From Napa County Airport (APC) to Henderson Executive Airport (HND)
Event
- NTSB case
- WPR09FA165
- 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
- Charter & commuter
- 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 200
- Aircraft type
- Beechcraft 200
- 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
- N257NA
- Operator
- Southern Nevada Jet Charter
- Onboard fatalities
- Unknown
- Route
- From Napa County Airport (APC), Napa County, CATo Henderson Executive Airport (HND), Henderson, NV
- 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 135: Air Taxi & Commuter
- 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
- Taxi · from runway
- Defining eventThe 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
- Ground collision
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The airline transport rated pilot landed the airplane and taxied to the operator's hangar. As the airplane approached the ramp, he observed a tug positioned in front of the hangar. He elected to turn the airplane directly towards the tug instead of the usual deplaning area. As he maneuvered the airplane, the right wing struck a tree located at the corner of the hangar. The right wing sustained substantial damage during the accident sequence. The pilot reported that he was familiar with the ramp area, and has had prior experience taxing in the area. The copilot was completing the post flight checklist at the time of the accident and did not observe the tree.
Probable cause
The pilot's failure to monitor and maintain clearance from an obstacle during taxi.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09FA165
- Event ID
- 20090325X03924
- Case number
- WPR09FA165
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2009-03-23.
- API snapshot SHA-256: 5ded0bc6653104f5280f10a4c21dd6ce6193633bb8d5808b88905dfe42926626; retrieved 2026-09-15T10:52:27.087Z.