Arefieva L.A. and Rusakov M.P. filed with the authority

  • USD
    • RUB
    • USD
    • EUR
i agree with "Terms for Customers"
Sold: 0
Uploaded: 29.03.2020
Content: S19-681.docx 12,73 kB

Product description


Arefieva L.A. and Rusakov M.P. submitted an application for registration of marriage to the registry office, but on the appointed day - November 26, 2003 - did not appear for registration, because Arefieva L.A. the night before, she was urgently hospitalized in connection with an exacerbation of a chronic disease. Every other day (November 28, 2003) Rusakov M.P. came to the registry office and asked to postpone the registration for another two months, because according to the opinion of the attending physician Arefyeva L.A. she will stay in hospital until the end of January 2004. The head of the registry office, referring to Art. 11 of the Insurance Code of the Russian Federation, postponed the registration day to December 26, 2003. But the couple did not appear at the registry office on that day, because Arefieva L.A. was still in the hospital. Then the head of the registry office returned their application for marriage by mail to MP Rusakov. Rusakov appealed against the actions of the head of the registry office to the court.
What should be the court decision?

Additional information

After payment you will be available a link to the solution of this problem in the file of MS Word. It should be noted that the problem solutions put up for sale were successfully handed over in the period 2009-2019 and could be outdated. However, the general algorithm will always remain true.

Feedback

0
Period
1 month 3 months 12 months
0 0 0
0 0 0
In order to counter copyright infringement and property rights, we ask you to immediately inform us at support@plati.market the fact of such violations and to provide us with reliable information confirming your copyrights or rights of ownership. Email must contain your contact information (name, phone number, etc.)

This website uses cookies to provide a more effective user experience. See our Cookie policy for details.