Jack LaSota

John A. ("Jack") LaSota is a former Arizona Attorney General (1977–1978). LaSota also served as Bruce Babbitt's Chief of Staff when the former was governor of Arizona.[1] He is a lobbyist[2] for the firm LaSota & Peters, P.L.C.[3]

Jack LaSota
20th Attorney General of Arizona
In office
1977–1979
Preceded byBruce Babbitt
Succeeded byRobert K. Corbin
Personal details
Political partyDemocratic

Career

LaSota is a member of the Arizona State Bar and has had a legal career. He has drafted statutes, including telephonic search warrant and electronic eavesdropping laws, many of which are still on the books. He spent three years at the Arizona State University College of Law as a faculty member and assistant dean, during which tenure his principal role was to draft and circulate nationwide to over 500 agencies pioneering Model Rules for Law Enforcement.

Attorney General

After Bruce Babbitt succeeded Wesley Bolin as governor, he appointed LaSota to replace him as Attorney General. Members of the Arizona senate, led by Senate President Ed Sawyer, sued LaSota arguing he was statutorily barred from serving. The senators alleged LaSota was barred by A.R.S. 41-191, which stated that "(t)he attorney general shall have been for not less than five years immediately preceding the date of taking office a practicing attorney before the supreme court of the state." While LaSota was employed at the Arizona State University School of Law his bar membership lapsed to retired status and, as a retired lawyer, he could not practice law or hold himself out as eligible to do so. The court voided the statute.[4]

Footnotes
  1. Career info on Jack LaSota
  2. Archived November 6, 2006, at the Wayback Machine Contact information for LaSota & Peters, P.L.C.
  3. LaSota & Peters, P.L.C.
  4. State ex rel. Sawyer v. LaSota, 119 Ariz. 253 (1978)
Legal offices
Preceded by
Bruce Babbitt		 Attorney General of Arizona
1978–1979		 Succeeded by
Robert K. Corbin


gollark: Why would people just create loads for no reason?
gollark: outnumber
gollark: In any sort of reasonable situation, the several hundred online users will vastly number API requests.
gollark: 1. screening of ideas in advance doesn't mean they'll have clean/good code2. people won't make hatcheries constantly for no reason3. yes, badly programmed ones might do stupid amounts of requests, but people will say "this is slow, avoid it"4. there would be few enough that TJ09 can complain at people who do it wrong - or just add rate-limiting
gollark: That does seem kind of unlikely.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.