The SMO…OTN is the coding that we use for IFR to VFR on top. Flight Aware seems to change all of the airport codes to add a ‘K’ to them. OTN, the airport, isn’t in the NAS computer (at least in ZLA), so it’s coded like a TEC route . . . SMO…OXR gives the routing SMO VNY OXR for example, and SMO…OTN gives the routing SMO V299 SADDE (where the pilot is either expected to cancel IFR or hold if still in IMC and advise of intentions). I wonder what would happen if someone filed an IFR flight plan from SMO to KOTN. It might be worth filing a flight plan before my next shift and seeing what comes out when I get there.
I don’t have the PEEER1 chart with me and it’s not available to the general public right now (to my knowledge). It’s only available to EJA aircraft with specific equipment codes (/L, /Q, I believe), which I am thinking that maybe you are since you know about it.
The climb gradient is probably for noise abatement. Aircraft departing runway 21 at SMO (when LAX is west - the only time we can use the PEEER1) will get a “fly runway heading until reaching the LAX 310-R, then turn right heading 265”, which basically means the aircraft will fly straight out until the shoreline for noise abatement, then turn right to join the LAX departure flow.
All IFR departures, whether on the PEEER1 or the standard departure procedure will be assigned an initial altitude of 3000’. The PEEER1 doesn’t go runway heading all the way to the shoreline, turns are allowed above an altitude, something like 650’ . . . or in that neighborhood. The people that live around the airport have regular noise protests, so the climb gradient is to appease them since the departure won’t be runway heading for more than a 1/2 mile off the runway.
I do not know Pete Elmore, does he work at the airport?