- Date
- February 16, 1974
- Place
- Boise City, OK · BOISE CITY, OK
- Injuries
- 2 fatal, 1 serious
- Phase of flight
- Approach
- Status
- Completed · report May 8, 1974
- Report
- Brief approved by the director
- FAA reports
- 19740216004762A19740216004761A
- Case key
- 186787
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-0636 74/2/16 BOISE CITY,OKLA HUGHES 269C CR- 1 0 0 MISCELLANEOUS COMMERCIAL, AGE 30, 1700 TIME - 1700 N8975F PX- 0 0 0 FERRY TOTAL HOURS, UNK/NR IN DAMAGE-DESTROYED OT- 1 1 0 TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - BOISE CITY MUNI DEPARTURE POINT INTENDED DESTINATION BOISE CITY,OKLA LAMAR,COLO TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH AIRCRAFT: BOTH IN FLIGHT TAKEOFF: INITIAL CLIMB PROBABLE CAUSE(S) PILOT IN COMMAND - EXERCISED POOR JUDGMENT MISCELLANEOUS ACTS,CONDITIONS - DISREGARD OF GOOD OPERATING PRACTICE PILOT IN COMMAND - FAILED TO SEE AND AVOID OTHER AIRCRAFT PERSONNEL - MISCELLANEOUS-PERSONNEL: PILOT OF OTHER AIRCRAFT FACTOR(S) PILOT IN COMMAND - FAILED TO USE OR INCORRECTLY USED MISC.EQUIPMENT SPECIAL DATA SEGMENTS OF AVIATION INVOLVED - SMALL US GEN.AV.-SMALL US GEN.AV. CONTROLLING AGENCY - NO CONTROL RADAR CTL/SURVEILLANCE - NOT UNDER RADAR CONTACT TRAFFIC ADVISORY ISSUED - OTHER CONTROLLED/UNCONTROLLED AIRPORT - UNCONTROLLED AIRPORT CONTROL ZONE/AREA - NO CONVERGENCE ANGLE-DEGREES - 0 HORIZONTAL COLLISION ANGLE-DEGREES - 0 VERTICAL COLLISION ANGLE-DEGREES - 0 EVASIVE ACTION TAKEN - NO ANTI-COLLISION LIGHTS - INSTALLED,OPERATION UNKNOWN REMARKS- CLIMBING L TURN ACROSS ACTIVE RWY.NOT MONITORING UNICOM.HIT ACFT ON FINAL APCH.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-0636 74/2/16 BOISE CITY,OKLA CESSNA 150 CR- 1 1 0 INSTRUCTIONAL COMMERCIAL, FL.INSTR., TIME - 1700 N22061 PX- 0 0 0 DUAL AGE 39, 10300 TOTAL DAMAGE-DESTROYED OT- 1 0 0 HOURS, UNK/NR IN TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - BOISE CITY MUNI DEPARTURE POINT INTENDED DESTINATION BOISE CITY,OKLA LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH AIRCRAFT: BOTH IN FLIGHT LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER IN-FLIGHT DECISIONS OR PLANNING PILOT IN COMMAND - SPONTANEOUS-IMPROPER ACTION PERSONNEL - MISCELLANEOUS-PERSONNEL: PILOT OF OTHER AIRCRAFT FACTOR(S) MISCELLANEOUS - EVASIVE MANEUVER TO AVOID COLLISION SPECIAL DATA SEGMENTS OF AVIATION INVOLVED - SMALL US GEN.AV.-SMALL US GEN.AV. CONTROLLING AGENCY - UNICOM RADAR CTL/SURVEILLANCE - NOT UNDER RADAR CONTACT TRAFFIC ADVISORY ISSUED - NONE CONTROLLED/UNCONTROLLED AIRPORT - UNCONTROLLED AIRPORT CONTROL ZONE/AREA - NO CONVERGENCE ANGLE-DEGREES - 0 HORIZONTAL COLLISION ANGLE-DEGREES - 0 VERTICAL COLLISION ANGLE-DEGREES - 0 EVASIVE ACTION TAKEN - YES ANTI-COLLISION LIGHTS - INSTALLED,OPERATION UNKNOWN REMARKS- DELAYED EVASIVE ACTION.TURNED INTO FLT PATH OF N8975F.
Aircraft · 2
- Registration
- N22061
- Reported as
- Cessna 150
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Boise City Muni
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.
- Registration
- N8975F
- Reported as
- Hughes 269C
- Category
- Helicopter
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Boise City Muni
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.
FAA reports on this event · 2
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.