DEN67I0030

NTSB incident investigation · Boeing 707 124 · Denver, CO · November 4, 1966

Incident · No injuriesClosed
Date
November 4, 1966
Place
Denver, CO · DENVER, CO
Injuries
39 uninjured
Damage
No damage
Phase of flight
Approach
Aircraft
N74612Boeing 707 124
Status
Completed · report May 8, 1967
Report
Brief approved by the director
Case key
119475

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

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
----------------------------------------------------------------------------------------------------------------------------
4-0038   66/11/4   DENVER COLO         BOEING 707 124      CR-  0  0  8  SCHED DOM PASSG SRV       CERTIFICATE UNKNOWN, AGE
        TIME - 1036                    N74612              PX-  0  0 31                            UNK/NR, UNK/NR TOTAL
                                       DAMAGE-NONE         OT-  0  0  0                            HOURS, UNK/NR IN TYPE,
                                                                                                   UNK/NR INSTRUMENT RATED.
        CLASSIFIED AS INCIDENT
        NAME OF AIRPORT - STAPLETON
        OPERATOR - CONTINENTAL AIR LINES,INC.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           MISCELLANEOUS                                            LANDING: FINAL APPROACH
        REMARKS- STABILIZER TRIM INOPERATIVE ON FINAL APPROACH.ACFT LANDED SUCCESSFULLY.

Aircraft

Registration
N74612
Reported as
Boeing 707 124
Category
Airplane
Engine
turbo jet
Damage
No damage
Airport
Stapleton

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.