SEA72D!A27

NTSB accident investigation · Piper PA-18 · Irwin, ID · March 23, 1972

Accident · No injuriesClosed
Date
March 23, 1972
Place
Irwin, ID · IRWIN, ID
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4716APiper PA-18
Status
Completed · report January 10, 1973
Report
Brief approved by the director
Case key
165658

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

NTSB brief

NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.

----------------------------------------------------------------------------------------------------------------------------
 FILE    DATE          LOCATION          AIRCRAFT DATA       INJURIES       FLIGHT                        PILOT DATA
                                                               F  S M/N     PURPOSE
----------------------------------------------------------------------------------------------------------------------------
3-1099  72/3/23    IRWIN,ID            PIPER PA-18         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 26, 360
        TIME - 1115                    N4716A              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 383 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          REXBURG,ID                  ROCK SPRINGS,WYO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - OTHER
        REMARKS- PLT LNDD ON A LARGE FROZEN LAKE.MN WHEELS BROKE THRU ICE.

Aircraft

Registration
N4716A
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.