LAX05LA236 · Sergent Great Lakes 2T1A
Sergent Great Lakes 2T1A · Accident: loss of control on ground/water during landing
From Phoenix Deer Valley Airport (DVT) to an unrecorded destination
Event
- NTSB case
- LAX05LA236
- 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
Sergent Great Lakes 2T1A
- Aircraft type
- Sergent 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
- N24LR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo not recorded
- 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
- 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
- Loss of control on ground/water
- 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
- Pilot in command › Directional control, not maintained
- Pilot in command › Ground loop/swerve, encountered
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The experimental tail wheel equipped airplane ground looped and nosed over during landing. According to the pilot, the airplane bounced slightly upon touchdown, and as it settled to the ground the second time, the airplane lurched to the right. The pilot added power and more left rudder, but that failed to correct the deviation. The airplane departed the runway, nosed over, and landed upside down. The right main landing gear wheel left a tire skid mark on the runway surface. The wind was reported at 7 knots and 20 degrees to the right from the runway centerline. The pilot said he believed that the right brake locked up on landing.
Probable cause
the pilot's failure to maintain directional control on landing roll, which resulted in a ground loop and nose over of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05LA236
- Event ID
- 20050824X01304
- Case number
- LAX05LA236
- 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: 897ee7581af89c88c54e7213e258498660079f58fd2c89ccaaa410a53fe1eb5b; retrieved 2026-09-22T05:38:47.872Z.