FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13CA263 · Garland Avipro Bearhawk

6 Jun 2013 · Sheridan, WY, United States

Garland Air Garland Avipro Bearhawk · Accident: aerodynamic stall/spin during initial climb

From Sheridan County Airport (SHR) to Johnson County Airport (BYG)

Report a problem

Event

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

Garland Avipro Bearhawk

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
N540TH
Operator
Garland Air
Onboard fatalities
Unknown
Route
From Sheridan County Airport (SHR), Sheridan, WYTo Johnson County Airport (BYG), Buffalo, WY
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
Initial climb
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
Aerodynamic stall/spin
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The pilot stated that the purpose of the flight was to return back to his home airport. He configured the airplane for a three-point takeoff and added full power. During the takeoff roll, the airplane began to veer to the left and subsequently became airborne. As the airplane ascended to about 50 feet above ground level (agl), the left wing dropped and subsequently struck the ground. The airplane was substantially damaged when it tumbled in a cartwheel-type maneuver with the right wing flipping over and striking the terrain. The airplane came to rest on its belly in a grassy area adjacent to the taxiway.

The pilot stated that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. He noted that the wind was calm. He thought that the airplane initially veered left because of p-factor and his delay in recognizing this aerodynamic phenomenon.

Probable cause

The pilot's failure to maintain airspeed, which resulted in a stall and a loss of aircraft control during the initial takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13CA263
Event ID
20130606X23054
Case number
WPR13CA263
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2013-06-07.
  • API snapshot SHA-256: 6b19b9c0ab5a37f6182e1007ca0e89f9c12c6373e0ef9899472386e40a6ad672; retrieved 2026-09-15T21:47:54.237Z.