- Date
- June 16, 1972
- Place
- Unadilla, GA · UNADILLA, GA
- Injuries
- 1 serious
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N7610VCallair A-9
- Status
- Completed · report March 15, 1973
- Report
- Brief approved by the director
- Case key
- 167226
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-3075 72/6/16 UNADILLA,GA CALLAIR A-9 CR- 0 1 0 COMMERCIAL COMMERCIAL, AGE 37, 427 TIME - 0615 N7610V PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 50 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION UNADILLA,GA LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS FACTOR(S) TERRAIN - HIGH OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 200 KIND OF OPERATION - DUSTING CROPS KIND OF CROP - OTHER TYPE OF CHEMICAL USED - DRY CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 357 SWATH RUN-HOW FLOWN - WIND CALM FIRE AFTER IMPACT
Aircraft
- Registration
- N7610V
- Reported as
- Callair A-9
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
N7610VRegistration cancelled May 25, 1973 · Aero Commander CALLAIR A-9BAirframe modelAero Commander CALLAIR A-9B
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.