Small Aircraft; High Wing; 1 Eng; Fixed Gear
Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Flight Crew Last 90 Days 128; Flight Crew Total 848; Flight Crew Type 791
Communication Breakdown
Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Took Evasive Action
Airport; Environment - Non Weather Related
My student who I was instructing at the time made his departure call from Runway 23 at Monroe. We cleared the runway visually and didn't see anyone. I always look at our oil pressure and temperature and verify airspeed alive which it was. We rotated at 60h and began to climb out. At about that time I saw another small aircraft right in front of us climbing out from opposite runway. I couldn't believe it! Where the hell did this aircraft appear from! Evasive action was needed so I took control and turned to the right approximately 30 degrees bank and 40 degree angle change to avoid collision. I called out frustrated but not mad aircraft departing Monroe opposite direction didn't you hear us announce departure to which they replied 'no we did not'. Going deeper into how this situation I think developed was the light and variable wind we had and the confusion it can create for which runway should be used. Also my student has a strong accent. Could it be the other pilots in the other plane didn't understand him? We had completed a radio check on UNICOM and had received a loud and clear so I know our radios were functioning properly. Another factor maybe our runway is highest in the middle and could have made it harder to see another aircraft 7;000 [feet] opposite end to see coming. This concludes my description of events of the runway incursion.
Small aircraft instructor reported on takeoff traffic took off opposite direction resulted in taking evasive action. Instructor reported runway is higher in the middle which may block transmissions.