Ariens 991163 Apex 60″ Fab Deck 24 HP Kawasaki Zero Turn Mower

$5,999.00

7 People watching this product now!

Ariens 991163 Apex 60″ Fab Deck 24 HP Kawasaki Zero Turn Mower


Features:
  • Featuring our most powerful engine, the 24 hp/726 cc Kawasaki® FR730
  • 60 fabricated deck is 5½ deep and made of 10-gauge steel
  • Fully tubular steel frame, Self-adjusting belt technology, High-Back Padded Seat and armrests, Foot-operated deck lift
Specs:

TITLE: APEX 60
ENGINE: Kawasaki® FR730
DISPLACEMENT (CC): 726 cc
DRIVE SYSTEM: Hydro-Gear® ZT-3100 Transaxles
FUEL CAPACITY: 5.1 Gallon (19.3L)
GROUND SPEED (APPROXIMATE MPH) (FWD/REV): 8 mph/4 mph
DECK MATERIAL: 10 ga
DECK CONSTRUCTION: Fabricated
NUMBER OF SPINDLES: 3
BLADE TIP SPEED (FPM): 18,000
SPINDLE MATERIAL: Aluminum
SPINDLE SHAFT: Steel
DECK DRIVE: Belt
DECK ENGAGEMENT: Electric Ogura®
DECK LIFT SYSTEM: Foot Operated
CUTTING WIDTH: 60 in
CUTTING HEIGHTS: 1.5-5 in
CUTTING POSITIONS: 15
WHEELS (FRONT): 13 x 6.5 in – 6 in
WHEELS (REAR): 22 x 12 in – 12 in
SEAT: High Back Premium w/ Padded Armrests
HOUR METER: Standard
WARRANTY (MACHINE): 4 year or 500 hours
WARRANTY (DECK & FRAME): 5 Year Limited
WEIGHT: 870 lbs
LENGTH: 79 in
WIDTH: 75 in
HEIGHT: 49 in
FRONT AXLE: Fixed

Accessories:
891008 2 Bucket Powered Bagger – Fits Apex models (Requires bagger mount kit and lower rops bagger mount kit)
791078 Lower Rops Bagger Mount (Required for installation of bagger on APEX units without a ROPS)
791066 60″ Bagger Mount Kit – Fits Apex models with 60 deck
791059 60″ Grass Mulching Kit – Fits Apex models with 60 deck
792105 60″ Operator Controlled Chute Baffle – Fits 60 Apex models
792134 60″ Discharge Cover Kit -Fits Apex models with 60 deck

Customer Reviews

0 reviews
0
0
0
0
0

There are no reviews yet.

Be the first to review “Ariens 991163 Apex 60″ Fab Deck 24 HP Kawasaki Zero Turn Mower”

Your email address will not be published. Required fields are marked *

You have to be logged in to be able to add photos to your review.

Online Sports Nutrition and Natural Dietetics.

Chances are there wasn't collaboration, communication, and checkpoints, there wasn't a process agreed upon or specified with the granularity required. It's content strategy gone awry right from the start. Forswearing the use of Lorem Ipsum wouldn't have helped, won't help now. It's like saying you're a bad designer, use less bold text, don't use italics in every other paragraph. True enough, but that's not all that it takes to get things back on track.

The villagers are out there with a vengeance to get that Frankenstein

You made all the required mock ups for commissioned layout, got all the approvals, built a tested code base or had them built, you decided on a content management system, got a license for it or adapted:

  • The toppings you may chose for that TV dinner pizza slice when you forgot to shop for foods, the paint you may slap on your face to impress the new boss is your business.
  • But what about your daily bread? Design comps, layouts, wireframes—will your clients accept that you go about things the facile way?
  • Authorities in our business will tell in no uncertain terms that Lorem Ipsum is that huge, huge no no to forswear forever.
  • Not so fast, I'd say, there are some redeeming factors in favor of greeking text, as its use is merely the symptom of a worse problem to take into consideration.
  • Websites in professional use templating systems.
  • Commercial publishing platforms and content management systems ensure that you can show different text, different data using the same template.
  • When it's about controlling hundreds of articles, product pages for web shops, or user profiles in social networks, all of them potentially with different sizes, formats, rules for differing elements things can break, designs agreed upon can have unintended consequences and look much different than expected.

This is quite a problem to solve, but just doing without greeking text won't fix it. Using test items of real content and data in designs will help, but there's no guarantee that every oddity will be found and corrected. Do you want to be sure? Then a prototype or beta site with real content published from the real CMS is needed—but you’re not going that far until you go through an initial design cycle.