FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Aero-Tech Services Raytheon Aircraft Company 58 UNDESIGNAT accident

25 Oct 2016 · Lancaster, PA, United States

Raytheon Aircraft Company 58 UNDESIGNAT · Accident: landing gear not configured

From Wings Field (LOM) to Lancaster Airport (LNS)

Report a problem

Event

NTSB case
GAA17CA074
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

Raytheon Aircraft Company 58 UNDESIGNAT

Aircraft type
Beechcraft 58
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
N600RV
Onboard fatalities
Unknown
Route
From Wings Field (LOM), Philadelphia, PATo Lancaster Airport (LNS), Lancaster, PA
Aircraft age
About 18 years (built 1998)
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
Landing
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
Landing gear not configured
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

  • Environmental issues › Physical environment

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot of the multiengine retractable landing gear airplane reported that during takeoff, two deer ran onto the runway as the airplane became airborne and that he heard and felt one of the deer hit the left main landing gear. He further reported that he diverted to an airport with an operating control tower, where he performed two passes in front of the tower, and was informed by tower personnel that it "appeared" that the left main landing gear was no longer "attached to the airplane". The pilot reported that he decided the best course of action was to land with the landing gear retracted, and on short final he moved the mixture controls to idle cut off, feathered the propellers, and turned both fuel selectors off. The airplane landed gear up and all persons on board evacuated immediately.

The airplane sustained substantial damage to the fuselage.

In an email exchange with the Director of Operations of the flight company, he reported that there were no reported mechanical anomalies with the airframe or engine prior to the deer impact.

The Federal Aviation Administration Chart Supplement airport page for the departure airport in part states: "Deer and large flocks of geese on and invof [in the vicinity of] arpt."

Probable cause

A collision with deer on the runway during the takeoff roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA074
Event ID
20161122X01429
Case number
GAA17CA074
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: 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: 98887035e57ddcb4ee01497697a42a7dea204cdbbe2bc39e45a038ed3f45074c; retrieved 2026-09-16T04:51:04.065Z.