You cannot simply merge single working networks.
In general, if you want to give your interfaces ip addresses, no matter if static or by DHCP, both interfaces must be on different subnets and routing must be enabled. For example eth0 has ip address 192.168.1.2/24 on subnet 192.168.1.0/24 with 255 ip addresses. Then wlan0 cannot be on the same subnet. You must configure a different subnet, e.g. ip address 192.168.2.2/24 on subnet 192.168.2.0/24 also with 255 ip addresses but different from subnet 192.168.1.0/24. The subnet is given by the bit mask
/24. Look at Wikipedia how subnetting works.
You have selected the whole private subnet 192.168.0.0/16 with 65536 ip addresses by bitmask
/16 so your both ip addresses are on the same subnet. This cannot work, except you use a bridge. But when using a bridge, slave interfaces eth0 and wlan0 cannot have an ip address. Also Raspberry Pi does not support bridging a client wifi connection. Bridging an access point works.
There is another issue with your router. You should only use one router entry, because it simplifies routing setup. The RasPi can take only one route to the internet at a time.
You told nothing about your local network. Do you need that all devices on wifi and on the wired network are have ip addresses from the same subnet? That's a so called broadcast domain and you need a bridge configuration for it. Or is it possible that wifi devices and wired connected devices have ip addresses from different subnets? Then you can setup routing.
This could be a configuration for routing but I haven't tested it. It is only to show the general idea. In dhcpcd.conf:
or the other way around, depending on your local network and where your router is available.
Enable routing in
# Uncomment the next line to enable packet forwarding for IPv4
To get an idea about the bridging thing you can look at Setting up a Raspberry Pi as an access point in a standalone network (NAT).