Date: 201601
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: Marginal
Weather elements / visibility: Icing; 6
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: CTAF ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Second reporter function: Dispatcher
Anomaly: Ground Excursion Taxiway; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Taxi
Result: General Maintenance Action
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Airport

Narrative: Following a normal landing with good braking action; the aircraft was slowed to taxi speed and continued to runway end. Reaching the left turn for taxiway C; braking action became nil. While entering taxiway; the nose wheel lost all steering traction and slid off taxiway. When stopped; passengers were deplaned normally through the main cabin door and transported to terminal via shuttle bus. Upon initial inspection by maintenance; no damage was found.


Second narrative: While preparing this flight release and going over the weather; it was clear that this flight needed an alternate based on the weather conditions at destination. Since the load was fairly light I decided to list the departure airport as the intended alternate. While going over the NOTAMs for destination Airport; I observed the MU readings to be well within the margin of safety for safe operation of this particular flight. Additionally; after reviewing NOTAMS for both airports there was nothing that stood out as a safety of flight issue. Although the runway conditions reported were issued several hours prior to flight release preparation; I did not call the airport to get current runway conditions. While flight following; I did not observe any hazardous weather or PIREPS enroute nor did I receive any updated NOTAMS for the Airport. I do remember seeing the aircraft make its initial descent into the terminal area and I observed the on-time register on my ACARS window. Sometime after that I received a phone call from the Captain advising me that she had landed but had slid off the runway/taxiway while trying to exit the end of the Runway. She let me know that the braking action was good when they landed but was poor towards the end. Hence; the aircraft sliding off of the end taxiway. She asked to be connected with Crew Support which I immediately did. As mentioned; I did not expect any safety of flight related issues while dispatching this flight. I did not receive any further updates; NOTAMS; field conditions; PIREPs while aircraft was enroute. I do however think the entire NOTAM system has been long overdue for an overhaul. If field conditions are such that require a NOTAM they should be required to update hourly or every two hours instead of just sitting in the NOTAM body for 24 hours. It is my understanding there are other companies that provide an 'in house' NOTAM system which would benefit our operation here overwhelmingly. I wish we had access to those additional resources. With technology as cutting edge as it is at this very moment the NOTAM system in its entirety is archaic. Furthermore; if braking action and mu values are marginal; then there should be a better system to notify airport users. Perhaps if MU values are '28/28/28' then they should be running MU tests and updating them hourly. It's not just about runway conditions taxiway conditions are important too! The NOTAM system is in desperate need of re-engineering. Things should be categorized in priority and in subsets. For example; an airport closure NOTAM should be at the very top. I also think if an airport is closed that should be the only NOTAM listed for that airport and should be spelled out AIRPORT CLOSED and NOT AP AD CLSD. Then all runway closures; runway conditions; etc. in one category. Then taxi way conditions; then NAVAID status; etc. It is time to streamline the process here. Let's implement a format that makes sense and works to make the National Airspace System that benefits planners; pilots; and passengers. After all; the entire world depends on aviation regardless of whether or not they purchase a plane ticket.


Synopsis: CRJ-200 Flight Crew and the Dispatcher involved described a taxiway excursion during exit from the runway after landing. The braking action for the runway had been reported as good on packed snow but the nose wheel steering was ineffective during exit from the runway and braking action was nil.