# Accident 20240223001269A: Luscombe 8E, Truth Or Conseq, NM, February 23, 2024

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 23, 2024, 08:45 local time
- Place: Truth Or Conseq, NM
- Airport: Truth Or Consequences Municipal
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 33.2354° N, 107.2699° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.2354&lon=-107.2699&mi=10
- Aircraft: N2669K, registered now (https://openairdocs.org/aircraft/N2669K) (OpenAirDocs)
- Registry model: Luscombe 8E (registry code 8190112, https://openairdocs.org/model/luscombe-8e) (OpenAirDocs)
- Registry engine: Continental C85 series (registry code 17008, https://openairdocs.org/engine/continental-c85-series) (OpenAirDocs)
- Reported make and model: LUSCOMBE 8E
- Reported engine: CONT MOTOR C85 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 1
- Pilot certificates: Private pilot
- Pilot flight hours: 130 total, 13 in this make and model, 20 in the last 90 days
- NTSB investigation: [NTSB WPR24LA102](https://openairdocs.org/ntsb/WPR24LA102) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20240223001269A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON FEBRUARY 23, 2024, AT 0845 MST, A LUSCOMBE 8E, SILVAIRE DELUXE, PERFORMED A GROUND LOOP DURING ITS LANDING ROLL WHILE ATTEMPTING A TOUCH AND GO AT TRUTH OR CONSEQUENCES MUNICIPAL AIRPORT (TCS) RUNWAY 31.  THE INSTRUMENT RATED PRIVATE PILOT SUFFERED MINOR INJURIES – A CUT HAND AND BRUISES ON HIS HEAD.  THE AIRCRAFT SUFFERED SUBSTANTIAL DAMAGE TO THE WING SPAR AND BUCKLING OF THE FUSELAGE.  THE PERSONAL FLIGHT ORIGINATED AT BELEN REGIONAL AIRPORT (BRG) IN VFR CONDITIONS ON FEBRUARY 23, 224 AT 0745 MST AND WAS ENROUTE TO LAS CRUCES INTERNATIONAL AIRPORT (LRU).  NO FLIGHT PLAN WAS FILED.

THE PILOT STATED THAT, BASED ON A WIND REPORT OF 330/5, HE OPTED TO PERFORM A TOUCH AND GO AT TCS AND THEN CONTINUE TO HIS DESTINATION.  HE STATED THAT HE FOUND HIS AIRSPEED BETWEEN THAT REQUIRED FOR A WHEEL LANDING AS OPPOSED TO A 3-POINT LANDING.  HE DECIDED TO EXECUTE A GO AROUND BUT DID NOT ADD SUFFICIENT POWER TO CLIMB.  AS HE ADDED POWER, HE LOST DIRECTIONAL CONTROL AND THE AIRCRAFT STARTED TURNING LEFT.  HE OVER CORRECTED WITH RIGHT RUDDER.  THE AIRCRAFT TOUCHED DOWN AND DEPARTED THE RUNWAY TO THE RIGHT.  HE APPLIED FULL BRAKING RESULTING IN A SKID THAT BROKE THE RIGHT MAIN GEAR AND FLIPPED THE AIRCRAFT ON ITS BACK.

BASED ON THE DESCRIPTION OF EVENTS, THE IIC FEELS THAT THE GROUND LOOP AND ACCIDENT WERE DUE TO A LACK OF THE PILOT'S KNOWLEDGE BASE.  THE ADDITION OF POWER WITH IMPROPER RUDDER APPLICATION IS ATTRIBUTABLE TO THE LEFT TURNING TENDENCIES ASSOCIATED WITH GYROSCOPIC PRECESSION, TORQUE, AND SPIRALING SLIPSTREAM.  IN THE CONFUSION, THE PILOT OVERCORRECTED WHICH EXACERBATED THE SITUATION.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB WPR24LA102](https://openairdocs.org/ntsb/WPR24LA102), Feb 23, 2024: Luscombe 8E (N2669K), Truth or Consequences, NM, substantial damage. Probable cause: The pilot’s failure to maintain airplane control during approach and landing that resulted in a runway excursion and subsequent impact with a berm.

## Other reports on N2669K (1)

Matched to the same aircraft by N-number and date.

- [Accident 19850608023419A](https://openairdocs.org/incident/19850608023419A), Jun 8, 1985: Luscom 8E (N2669K), Albuquerque, NM, Substantial damage. Main gear folded back during wheel landing. Clevis bolt which attaches jack strut to main strut failed.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.