# NTSB OAK77DXQ08: Piper PA-24, N7506P, Hawthorne, NV, February 26, 1977

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Closed
- Date: February 26, 1977
- Place: Hawthorne, NV · HAWTHORNE, NV
- Location: 38.5253° N, 118.6260° W: Placed by OpenAirDocs: center of Hawthorne, NV, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.5253&lon=-118.6260&mi=10
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report April 27, 1977
- Report: Brief approved by the director
- NTSB case key (mKey): 157726
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=OAK77DXQ08
- Page: https://openairdocs.org/ntsb/OAK77DXQ08

## NTSB brief

```
----------------------------------------------------------------------------------------------------------------------------
 FILE    DATE          LOCATION          AIRCRAFT DATA       INJURIES       FLIGHT                        PILOT DATA
                                                               F  S M/N     PURPOSE
----------------------------------------------------------------------------------------------------------------------------
3-0439  77/2/26    HAWTHORNE,NV        PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 42, 542
        TIME - 0835                    N7506P              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 133 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HAWTHORNE
        DEPARTURE POINT             INTENDED DESTINATION
          TULARE,CA                   HAWTHORNE,NV
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: DESCENDING
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           POWERPLANT - ENGINE STRUCTURE: MASTER AND CONNECTING RODS
           MISCELLANEOUS ACTS,CONDITIONS - MATERIAL FAILURE
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - NOT ALIGNED WITH RUNWAY/INTENDED LANDING AREA
           MISCELLANEOUS - SMOKE IN COCKPIT
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT.
        REMARKS- NUMBER 3 CONNECTING ROD FAILED OVER AIRORT AT APPROX 2700FT.
```

## Aircraft

- Registration: [N7506P](https://openairdocs.org/deregistered/N7506P-2013-06-05), registration cancelled 2013-06-05, S/N 24-2707, built 1961 (OpenAirDocs)
- Reported make and model: PIPER PA-24
- Registry model: [Piper PA-24-250](https://openairdocs.org/model/piper-pa-24-250) (registry code 7102404) (OpenAirDocs)
- Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs)
- Category: Airplane
- Engines: reciprocating
- Damage: Substantial damage
- Airport: Hawthorne

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 19770226003899A](https://openairdocs.org/incident/19770226003899A), Feb 26, 1977: Piper PA24250, Hawthorne, NV, Substantial damage. Number 3 connecting rod failed over airort at approx 2700FT.

## Other investigations on N7506P (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 OAK75DVA17](https://openairdocs.org/ntsb/OAK75DVA17), Sep 3, 1974: Piper PA-24 (N7506P), Coalinga, CA, substantial damage

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.

---
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.
