C172 flight instructor reported a near midair collision after departing aao.

Attributes
ACN	1501114
Time
Date	201712
Local Time Of Day	0601-1200
Place
Locale Reference	AAO.Airport
State Reference	KS
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Flight Plan	None
Aircraft 2
Make Model Name	Zenith Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Other Unknown
Person 1
Function	Instructor
Qualification	Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument
Experience	Flight Crew Last 90 Days 100 Flight Crew Total 3000 Flight Crew Type 900
Events
Anomaly	Conflict NMAC Deviation - Procedural Published Material / Policy
Miss Distance	Horizontal 0 Vertical 200

Narrative:

[I] checked both communication radios with the airport base station using the unicom/CTAF frequency. The aao ASOS reported winds to be 4 to 6 kts from 10 degrees magnetic; indicating that runway 36 should be used. The wind socks also indicated that runway 36 should be used.the student pilot taxied to the runway 36 run up pad and completed a pre-takeoff check. Prior to takeoff; the pilots on board visually looked for traffic and listened on the CTAF frequency. No other traffic was observed or heard. On CTAF the student pilot announced that he was taking off on runway 36; taxied onto the runway and took off. Nearing the north end of the 6000 ft runway; climbing through 400 or 500 ft AGL; [we] both observed a yellow-colored target at [our] altitude on the onboard ads-B flight information system (fis). Seconds later the conflicting aircraft; believed to be a CH2T aircraft; was observed passing below [us] and then arcing to a sse track. No communications were ever heard from the conflicting aircraft.note: the fis indicates conflicts; but does not recommend a course of action.[I] believe that the CH2T was practicing runway 18 ILS approaches to aao. Aircraft practicing instrument approaches into aao normally make several announcements on the CTAF frequency - particularly when the approach is opposite the active runway direction.

Original NASA ASRS Text

Title: C172 flight instructor reported a NMAC after departing AAO.

Narrative: [I] checked both communication radios with the airport base station using the Unicom/CTAF frequency. The AAO ASOS reported winds to be 4 to 6 kts from 10 degrees magnetic; indicating that runway 36 should be used. The wind socks also indicated that runway 36 should be used.The student pilot taxied to the runway 36 run up pad and completed a pre-takeoff check. Prior to takeoff; the pilots on board visually looked for traffic and listened on the CTAF frequency. No other traffic was observed or heard. On CTAF the student pilot announced that he was taking off on runway 36; taxied onto the runway and took off. Nearing the north end of the 6000 ft runway; climbing through 400 or 500 ft AGL; [we] both observed a yellow-colored target at [our] altitude on the onboard ADS-B Flight Information System (FIS). Seconds later the conflicting aircraft; believed to be a CH2T aircraft; was observed passing below [us] and then arcing to a SSE track. No communications were ever heard from the conflicting aircraft.Note: the FIS indicates conflicts; but does not recommend a course of action.[I] believe that the CH2T was practicing Runway 18 ILS approaches to AAO. Aircraft practicing instrument approaches into AAO normally make several announcements on the CTAF frequency - particularly when the approach is opposite the active runway direction.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.