Baron 55/Cochise
Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Flight Crew Last 90 Days 70; Flight Crew Total 980; Flight Crew Type 75
Situational Awareness
Conflict Airborne Conflict
Flight Crew Took Evasive Action
Human Factors
After listening to the ATIS and determining the winds were calm; I taxied to Runway 25R via Alpha. The CTAF at that time indicated an aircraft was approaching from the north. No other traffic was heard and a visual inspection of the airport grounds did not reveal any other aircraft. After holding short of 25R momentarily for a second audio & visual inspection of the surrounding area; I called out and took off on runway 25R. At the departure end of 25R; I noticed Aircraft Y ([a] training aircraft) rotate and lift off of Runway 7R in the opposite direction. I was higher than Aircraft Y and initiated my turn to the north away from Aircraft Y per the DVT1 instrument departure at this time (right turn out). There was vertical and horizontal separation at all times; but it was obvious that near-simultaneous departures from opposite parallel runways reduced the margin of safety and was not ideal.In this instance; visual and CTAF monitoring on 118.4 did not work effectively. The rising sun further complicated visual recognition due to glare from buildings and the surrounding environment. I had no issues communicating with departure or approach on both radios in my aircraft and the volume was turned up audibly on both radios. So; I am unsure if the other aircraft were making radio calls or if my aircraft did not receive them. Furthermore; a calm wind runway was not designated in the Airport Facility Directory. I believe this situation could also have been avoided in the future by designating a calm wind runway in the airport facility directory so all aircraft use the same runway.
Baron 55 pilot reported an airborne conflict after taking off from DVT on Runway 25R and spotting an unannounced aircraft taking off from 7R.