WPR10CA282 · Great Lakes 2T-1A-2
Chandler Air Service Great Lakes 2T-1A-2 · Accident: loss of control on ground during landing
From Chandler Municipal Airport (KCHD) to Chandler Municipal Airport (KCHD)
Event
- NTSB case
- WPR10CA282
- 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
Great Lakes 2T-1A-2
- Aircraft type
- Great Lakes 2
- 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
- N6075L
- Operator
- Chandler Air Service
- Onboard fatalities
- Unknown
- Route
- From Chandler Municipal Airport (KCHD), Chandler, AZTo Chandler Municipal Airport (KCHD), Chandler, AZ
- 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 · landing roll
- 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
- Loss of control on ground
- 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 › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After performing air work, the certificated flight instructor (CFI) and airline transport pilot (ATP) returned back to the airport where the ATP would conduct touch-and-go practice takeoffs and landings in the tailwheel-equipped airplane. The first three landings were uneventful and they had planned for the fourth to be a full stop with the airplane configured for a three-point landing. Following a normal approach and touchdown, the airplane was on the landing roll when it suddenly turned to the left 30 degrees relative to the runway centerline. Both pilots applied full right rudder, but the airplane continued the left turn and exited the runway surface. The airplane ground looped, coming to rest facing approximately 270 degrees from the runway centerline. The pilots both reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine.
Probable cause
The pilot’s failure to maintain directional control and the flight instructor's inadequate remedial action during the landing roll, which resulted in a ground loop.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA282
- Event ID
- 20100609X55252
- Case number
- WPR10CA282
- 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: 685e8c6a151b9cb60eb71459a4406b7d95880ca2e5804f1f896a13945e7271e7; retrieved 2026-09-15T14:25:57.586Z.