<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Grampian Conditions/Certificates</title>
  <link rel="self" href="https://khub.net/c/message_boards/find_thread?p_l_id=53683759&amp;threadId=26005287" />
  <subtitle>Grampian Conditions/Certificates</subtitle>
  <id>https://khub.net/c/message_boards/find_thread?p_l_id=53683759&amp;threadId=26005287</id>
  <updated>2026-07-16T19:59:41Z</updated>
  <dc:date>2026-07-16T19:59:41Z</dc:date>
  <entry>
    <title>Grampian Conditions/Certificates</title>
    <link rel="alternate" href="https://khub.net/c/message_boards/find_message?p_l_id=53683759&amp;messageId=26005286" />
    <author>
      <name>Former Member</name>
    </author>
    <id>https://khub.net/c/message_boards/find_message?p_l_id=53683759&amp;messageId=26005286</id>
    <updated>2016-07-27T12:01:34Z</updated>
    <published>2016-07-27T12:01:34Z</published>
    <summary type="html">&lt;p&gt;A major residential application has been submitted with its main&amp;nbsp;access from an unadopted&amp;nbsp;byway together with&amp;nbsp;a&amp;nbsp;Certificate C ie unknown owners. There are thought to be 4&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; separate owners of the byway but the developer obviously has no agreement with them. The&amp;nbsp;&amp;nbsp;Planning Officer would like to recommend approval subject to a Grampian Condition to improve the access. Given the Merritt Case and others:&lt;/p&gt;

&lt;p&gt;Is the certificate acceptable?&lt;/p&gt;

&lt;p&gt;Is such a condition ultra vires? Is there any 'reasonable propect' of implementation within the usual time limits given that the 4 owners have a share of a ransom strip?&lt;/p&gt;

&lt;p&gt;(The Planning Authority may be willing to make a CPO afterwards.)&lt;/p&gt;

&lt;p&gt;Very unusual!&lt;/p&gt;

&lt;p&gt;Many thanks for any views.&lt;/p&gt;</summary>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2016-07-27T12:01:34Z</dc:date>
  </entry>
</feed>
