Legal Opinion

Tucker v. Commissioner

United States Tax Court

Decided February 23, 1971No. Docket No. 4881-69PublishedCited by 195 opinions

The petitioner found no suitable employment in the vicinity of his family residence, so he accepted positions in other localities, but did not change his residence. He had no business ties to the area of his residence. No travel was required in the course of his work. Held, his duplicate living expenses were incurred because of his personal choice of a place of residence rather than because of the demands of his trade or business, and therefore are nondeductible.

1Opinion of the Court

Simpson, Judge:

The respondent determined a deficiency of $364.45 in the income tax of the petitioners for 1967. The issue for decision is whether one of the petitioners was away from home for tax purposes during parts of the taxable year in issue.

FINDINGS OF FACT

Some of the facts have been stipulated, and those facts are so found.

The petitioners, Truman C. Tucker and Birdie Jo Tucker, filed a joint Federal income tax return for 1967 with the district director of internal revenue, Nashville, Tenn. They maintained their residence in Knoxville, Tenn., when the petition was filed in this case.…

2Cases cited11 opinions

  1. Commissioner v. FlowersSupreme Court of the United States · 1946
  2. Kroll v. CommissionerUnited States Tax Court · 1968
  3. Michaels v. CommissionerUnited States Tax Court · 1969
  4. Garlock v. CommissionerUnited States Tax Court · 1960
  5. Bixler v. CommissionerUnited States Board of Tax Appeals · 1927

6 more not listed; retrieve them via the Exa API.

3Cited by195 opinions

  1. Mitchell v. CommissionerUnited States Tax Court · 1980
  2. Norwood v. CommissionerUnited States Tax Court · 1976
  3. Hynes v. CommissionerUnited States Tax Court · 1980
  4. Daly v. CommissionerUnited States Tax Court · 1979
  5. Bochner v. CommissionerUnited States Tax Court · 1977

190 more not listed; retrieve them via the Exa API.

Showing a preview — retrieve the full document via the Exa API.

Powered by the Exa API