Date: 201903
Local time of day: 1201-1800
Location: HUA.Airport, AL
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class G HUA
ATC / advisory: CTAF HUA
Second aircraft: Small Aircraft
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: After performing a radio check with Approach Control; I switched back to the HUA CTAF and announced our (my student and I) intentions to depart Runway 35 to the north. As my student taxied on taxiway Alpha; I reminded her of the importance of scanning all around the field for any other air traffic or conflicts. We were both looking and neither of us saw any other aircraft. The ASOS reported; '...clear skies below 1-2 thousand.' It was a beautiful day. Lining up on the centerline; we kept the airplane rolling with my student applying full power. As I always do; I check and call out: 'engine instruments are in the green...power set...airspeed is alive.' We reached 50 kts; my student rotated; and we were airborne; it was her best takeoff to date and I was thrilled. I then turned nearly all of my attention to directly in front of us while peeking at the instrument panel to ensure all remained well. While within 25 feet of the runway; I think; at nearly the same moment; we both saw an airplane flying directly at us. When I first saw the airplane; I estimate that it was about 1;000 to 1;500 feet ahead of us and about 150 above us but it didn't seem to be descending towards the runway. Taking control of our airplane; I descended and then brought us to a level pitch attitude about 10 feet above the runway. About 3 seconds later; our two airplanes crossed paths; one going north; one going south; no lateral separation; and about 150 feet of vertical separation. I am convinced that had I not descended and leveled our airplane; we would have climbed into the path of the southbound airplane.Perceptions; judgments; decisions: When I first saw the airplane flying directly at us; I thought it was one of our flying club's and that they had been given a practice approach to Runway 17 [opposite direction]. I couldn't believe that they weren't talking on the radio and I was determined to figure out who the pilot was. Because I assumed it was a club airplane and perhaps a 'weekend warrior' pilot; I didn't report the NMAC to Approach Control. It turned out that it was not one of our airplanes. A pilot who witnessed the entire chain of events spoke with me afterward and he said that he saw the airplane pass over us; start a shallow climb; raise his landing gear; and then make a sharp turn to the west/northwest; but that the airplane remained low to the ground (500-1;000 feet AGL) before climbing to perhaps 2;000 feet and flying off to the northwest.Actions or inactions: I was very happy that when presented with a critical situation with seconds to make a decision; my thought process was clear; I knew what had to be done; and I did it; keeping my student and I (and the other airplane's occupants) safe. However; I should have reported the NMAC to Approach Control so that maybe they could have determined who was flying the errant airplane.




Synopsis: GA flight instructor reported an NMAC with opposite direction traffic after takeoff from HUA non-towered airport.