- Date
- September 6, 1968
- Place
- Hollister, CA · HOLLISTER, CA
- Injuries
- 1 uninjured
- Damage
- Destroyed
- Phase of flight
- Takeoff
- Aircraft
- N9768ZNorthrop P-61A
- Status
- Completed · report October 31, 1968
- Report
- Brief approved by the director
- Case key
- 108197
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-3059 68/9/6 HOLLISTER,CALIF NORTHROP P-61A CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 43, 4850 TIME - 1710 N9768Z PX- 0 0 0 ASSOC FIRE CTL ACTIVITY TOTAL HOURS, 377 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - HOLLISTER TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: OBJECT TAKEOFF: ABORTED PROBABLE CAUSE(S) PILOT IN COMMAND - DELAYED ACTION IN ABORTING TAKEOFF FACTOR(S) WEATHER - HIGH TEMPERATURE WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE CLEAR UNLIMITED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE RELATIVE BEARING OF WIND NONE RIGHT QUARTERING HEAD WIND 023-067 DEGREES TEMPERATURE-F WIND DIRECTION-DEGREES 90 270 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 10 VFR TYPE OF FLIGHT PLAN NONE FIRE AFTER IMPACT REMARKS- TEMP 90 DEG. ACFT LOADED WITH BORATE,RAN THROUGH FLDS,STRUCK FENCE AND SLOPE OF HILL.
Aircraft
- Registration
- N9768Z
- Reported as
- Northrop P-61A
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Hollister
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.