- Date
- July 19, 1971
- Place
- Laurel, MT · LAUREL, MT
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N8264HCallair A-9
- Status
- Completed · report March 9, 1972
- Report
- Brief approved by the director
- Case key
- 162388
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-2724 71/7/19 LAUREL,MONT CALLAIR A-9 CR- 0 0 1 NONCOMMERCIAL COMMERCIAL, AGE 25, 338 TIME - 1815 N8264H PX- 0 0 0 PRACTICE TOTAL HOURS, 1 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - LAUREL DEPARTURE POINT INTENDED DESTINATION LAUREL,MONT LOCAL TYPE OF ACCIDENT PHASE OF OPERATION STALL IN FLIGHT: PROCEDURE TURNAROUND PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED FACTOR(S) PILOT IN COMMAND - LACK OF FAMILIARITY WITH AIRCRAFT WEATHER - HIGH DENSITY ALTITUDE 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 TEMPERATURE-F NONE 84 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 60 9 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- PRACTISING SWATH RUNS. FIRST FLT IN TYPE ACFT. DENSITY ALT ABOUT 6000 FT.
Aircraft
- Registration
- N8264H
- Reported as
- Callair A-9
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Laurel
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.