I believe that this is incorrectly simplistic, if only because these sorts of situations by definition exist at the interface between a railroad and either a private or government road. Having the line operator (which I'm taking to mean railroad owner, in this case BNSF) bear 100% of the burden of providing full crossing protection creates an unbalanced situation (in terms of the cost to be borne). I'm not an expert, but have been following a forum thread on this topic (this Amtrak-truck collision and how to prevent repeats)[0] which points to articles stating that this particular crossing has been "on the list" of not the RR owner (BNSF) but MODOT (Missouri [state] Dept of Transportation) for receiving a "crossing gates and lights" (automated protection) deployment, and that the cost of this prospective deployment is approximately USD400K (per crossing) which would be
shared by the state (MODOT) and BNSF, and that, as noted by others posting in this thread, there are a large number (probably the majority) of RR/road crossings in the state (and country) which are similarly unprotected, and whose low use rate has historically not justified the installation and ongoing maintenance costs of full crossing protection. A cynic on the linked[0] thread mentioned it was possible that MODOT had put
every unprotected RR/road crossing "on the list" to receive a full protection equipment deployment, so that in case of any similar accident, they could claim to "already be working on a solution, just didn't get there in time" as in bureaucratic CYA.
Given the costs involved, IMO it would probably be better to close at least half of the crossings in (e.g. relatively flat farmland) areas where the road grid incurs these crossings at a rate more than one per mile. But as with decisions to spend money, choosing which crossings to close (ostensibly so that the remainder may have automated protection added) becomes a political "hot potato" that can easily cause the process to stall.
[0] https://cs.trains.com/trn/f/111/t/292768.aspx
[1] https://www.kansascity.com/news/state/missouri/article263049...